SBo scripts not building on current (read 1st post, pls)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
the SBo packages for 14.2 six and python3-six are equivalent, in content, of the six package in Slackware current (six there contains also the python3 stuff so python3-six has been removed from the repository to avoid overlapping), so I think you should be ok.
checking for OCaml findlib package num... not found
configure: error: package num is required. It should be part of your ocaml installation.
I guess this https://github.com/ocaml/num is missing or ocaml version is too old. A quick git log -i --grep='ocaml-num' shows that ocaml-num has never been added.
Last edited by average_user; 02-14-2020 at 07:43 AM.
I personally like a lot the newly addition of qt5 in current but, for what matters this repository, it will mean that the stuff depending on qt5 here will be most probably broken and it will take some time to fix it: please be patient...
if anyone has patches that are already tested and working they are much appreciated, thanks in advance!
I personally like a lot the newly addition of qt5 in current but, for what matters this repository, it will mean that the stuff depending on qt5 here will be most probably broken and it will take some time to fix it: please be patient...
if anyone has patches that are already tested and working they are much appreciated, thanks in advance!
If there is anything that you need help with, just give us a list.
Since the Feb 13 update in current, /var/run is mounted as tmpfs, so everything are deleted when shutting down slackware.
Some daemons (tor, opendmarc, opendkim for example) need a /var/run/pid-path-for-daemon folder to store their pid file.
Maybe it's time to create these folders when running "/etc/rc.d/rc.mydaemon start"?
I started, for my personnal use, to create a "/etc/default/mydaemon" with:
I agree that the best place to create the folders would be when starting the daemon.
those data could also be set directly in rc.mydaemon without using an additional /etc/default/mydaemon file but also with it should be perfectly fine, it's just a matter of taste, I think: I'm saying this because actually there's no need to use a generic way as we don't use predefined functions to start and stop services (like other distro do).
Last edited by ponce; 02-16-2020 at 04:56 AM.
Reason: clarified a little
if can be useful for testing I upgraded qt5-webkit and PyQt5 (that actually includes also python3-PyQt5), but they aren't merged in the main current branch yet
I agree that the best place to create the folders would be when starting the daemon.
those data could also be set directly in rc.mydaemon without using an additional /etc/default/mydaemon file but also with it's fine, it's just a matter of taste, I think: I'm saying this because actually there's no need to use a generic way as we don't use functions to start and stop services (like other distro do).
OK. I think you're right about /etc/default/mydaemon. It could be used but not needed.
Thanks to Seb on french slackware forum who helped me to find the better way.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.