increment release number
hang on a min, i realize that because i did git rebase, i need to rebuild to update the release number and update the diff.
Wed, Oct 2
btw, I packaged it locally. Both the x11 and gl versions worked swimmingly. On pdf files containing large vector graphics, evince/okular are extremely slow in rendering, but mupdf renders instantly.
Tue, Oct 1
remove python2 support
The patch actually applies cleanly. Remove .rej/.orig files that implied otherwise.
remove python2 version, and remove some dependencies accordingly.
I only need its python3 version.
updated with proper packager setup
revised package description.
Fri, Sep 27
Rebuild and tested against python-cryptography (D6539)
Jul 29 2019
abandoning this patch in favor of D6539
Jul 26 2019
homepage url updated to use https
@Jacalz Sorry I didn't search properly before i submit this patch. I was updating paramiko, which requires the new version of python-cryptography.
I only have experience with paramiko, and never used the packages JoshStrobl mentioned. Perhaps @JoshStrobl wants to coordinate the testing effort.
Jul 25 2019
Jun 24 2019
Jun 17 2019
May 19 2019
move sample config to /usr/share/defaults; use 5-digit permission
fix version number.
May 17 2019
that was embarrassing... fixed.
fix PREFIX so files get installed in /usr instead of /usr/local
May 14 2019
open-modelica is not one package, it'd be a group of 6-7 packages. I have a recent project that involves modelica, but only touches a small portion of the software. I'm afraid that even if I prepared the packages for solus, I won't be able to adequately verify that the build was correct.
May 11 2019
electronic-wechat was removed from repo because it's not maintained. I tried several of its forks, and found the following two promising :
Apr 30 2019
I have a patch to submit, but wondering if it should include the server binary.
If the server executable is included, i feel obliged to add the default config file and systemd service unit file. However I don't think I feel comfortable to enable nbd service.
Apr 28 2019
I'd say it's quite reasonable to include nbd client in solus.
Apr 20 2019
@kyrios123 sure thanks.
Apr 14 2019
Apr 9 2019
@JoshStrobl a gentle reminder that requred change has been made, request another review
Apr 6 2019
Apr 2 2019
Apr 1 2019
Feb 13 2019
@jeos fcitx works well for me (Chinese input). It had been proposed for inclusion in #T1298 but rejected.
Feb 3 2019
Jan 2 2019
abandoned in favor of D4924.
Dec 8 2018
Oct 21 2018
Oct 18 2018
fix builddep: bdb5
I see that libpinyin depends on Berkeley db 5, which is in the base image. According to abi_used_libs, it has always been depending on bdb5.
I don't understand why it requires bdb 4 in your build environment. Could it be some package in local repo?
Oct 16 2018
btw, astroid uses scdoc or ronn to build man page. neither is available in solus yet, so skipping docs for now.
update to 0.14; withdraw previous proposal tto export XAPIAN_CJK_NGRAM
Oct 1 2018
I avoid taking sides in the fcitx v.s ibus debate, but hope to include fcitx in the repo.
Sep 30 2018
removed old .eopkg files in the directory, such that abireport does not
report dependencies on Qt4, which was used by the older klayout builds.
Even with the ibus-daemon -drx workaround, ibus is almost unusable (at least with ibus-libpinyin). ibus will freeze all keyboard inputs frequently, which requires ibus-daemon is restarted.
In some cases, the ibus-daemon restart will cause budgie-wm to crash.
Sep 22 2018
One point of concern:
If we take the /etc/profile.d appraoch, once astroid is installed on that machine, all applications using the xapian library will see XAPIAN_CJK_NGRAM=1.
I'm afraid this would surprise users who have been using xapian prior to installing astroid.
Sep 19 2018
Sep 14 2018
I find it mysterious. The build log shows the following dependency discovery (Qt5 only) :
Sep 13 2018
After submission, I'm not sure why abireport added the following lines to abi_used_libs. I'm pretty sure Qt4 wasn't even present in the chroot build environment.
Sep 4 2018
Sep 3 2018
move sample config file to /usr/share as requested.
Aug 28 2018
Frankly ibus has been a constant source of trouble for years. I had better luck with fcitx on Ubuntu since 14.04. I wonder what's reason of choosing ibus over fcitx in solus/budgie?
May 22 2018
Thanks @born2discover, i think that's ample examples of application, and i think enough people care about RabbitMQ to keep it maintained.
May 2 2018
@born2discover i agree with you that developers need it. Could you please list some software framework that relies on RabbitMQ?
Apr 21 2018
Apr 13 2018
Mar 25 2018
@ThanosApostolou you are right. _LARGEFILE64_SOURCE is for building on 32bit system. Since Solus is 64bit only, that macro is not needed.
tested with a few .vcd files. works for me. i don't have examples to test its tcl scripts.
Mar 24 2018
This is the only open-source digital waveform viewer that is usable.
Mar 20 2018
Happy to report that I tested @ThanosApostolou's diff after updating to the latest stable. Both verilog simulation and VPI plugin building work well.
Mar 18 2018
try again to mention the tasks
Mar 17 2018
As for static libraries, are those plugins compiled as separate packages or at run-time via iverilog itself? If yes, I agree they can stay in. If no, they belong in -devel
Do you think that office.scientific is a more suitable component than programming?
On one hand verilog is a programming language, on the other it is almost exclusively used for electronics hardware design.
I believe iverilog should fall in the same component as kicad and klayout. There is no engineering component in solus, hence office.scientific.