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.
1.
Add optional dependencies for KDE/Kstars: libev, libnova, wcslib, stellarsolver, libindi (all on SBo). The thirdparty drivers and deps can be left on SBo. See discussion: https://www.linuxquestions.org/quest...1/#post6375537
2.
Move Kstars from Slackware tree to SBo to allow the above deps to be incorporated as needed. I guess the libinidi maintainer could pick up Kstars (the fool).
Reason:
libindi and stellarsolver are picked up at Kstars compile time if found. Kstars source already includes EKOS, an INDI client for computer control of astronomy devices such as CCD cameras (astrophotography) and telescope movement control, etc.
1.
Add optional dependencies for KDE/Kstars: libev, libnova, wcslib, stellarsolver, libindi (all on SBo). The thirdparty drivers and deps can be left on SBo. See discussion: https://www.linuxquestions.org/quest...1/#post6375537
2.
Move Kstars from Slackware tree to SBo to allow the above deps to be incorporated as needed. I guess the libinidi maintainer could pick up Kstars (the fool).
Reason:
libindi and stellarsolver are picked up at Kstars compile time if found. Kstars source already includes EKOS, an INDI client for computer control of astronomy devices such as CCD cameras (astrophotography) and telescope movement control, etc.
I for one, I would like this:
3. Leave the KStars alone and as it is.
Reason:
Let's stop complicating the Slackware just because someone uses it to control his astronomical telescope. Or he/she/it debugs the kernel, or whatever else feature expected to be used only by a particular individual.
So, dear @kingbeowulf please be kind to leave the KStars alone!
1.
Add optional dependencies for KDE/Kstars: libev, libnova, wcslib, stellarsolver, libindi (all on SBo). The thirdparty drivers and deps can be left on SBo. See discussion: https://www.linuxquestions.org/quest...1/#post6375537
2.
Move Kstars from Slackware tree to SBo to allow the above deps to be incorporated as needed. I guess the libinidi maintainer could pick up Kstars (the fool).
Reason:
libindi and stellarsolver are picked up at Kstars compile time if found. Kstars source already includes EKOS, an INDI client for computer control of astronomy devices such as CCD cameras (astrophotography) and telescope movement control, etc.
In the 2nd case, can kstars be re-compiled even if it's part of slackware and not SBo?
A similar case is ffmpeg -- I installed zimg from SBo and re-compiled ffmpeg for zimg support. No need to move ffmpeg to SBo.
I would suggest the next big changes in current would be updating OpenSSL to 3.0.
The current 1.1.1's support will be ended on 2023-09-11, by the time new Slackware release, 1.1.1 maybe out of support or close to. This sure causing lots of rebuild and patches.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
