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.
Personally I wouldn't mind seeing a tiling window manager ootb in slackware, spectrwm and i3 would be good contenders for their relative simplicity and ease of use. Spectrwm for those that want something more efficient and minimal and i3 for those that want eye candy. However they are easy to add yourself and I'm not sure enough people would use them for it to be justified.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Yeah, on second thoughts I'm actually inclined to agree with you there. To someone who started when computer memory was still counted in units of K -- and single figure amounts at that -- 12M seems an outrageous amount. I guess I've just become accustomed to seeing the large size of modern day applications.
Yeah, on second thoughts I'm actually inclined to agree with you there. To someone who started when computer memory was still counted in units of K -- and single figure amounts at that -- 12M seems an outrageous amount. I guess I've just become accustomed to seeing the large size of modern day applications.
I'm still amazed at the size of some of the APKs for Android. My banking app is 77MB! That's more than most of the games I have installed.
Hopefully not reading all 35 pages won't have been too lazy on my part and if someone mentioned it this will just be an additional vote. Why oh why is Digikam not included in the Recommended KDE-based full install? Almsot everyone has a digital camera and many of Digikam's dependencies are also needed for other important multimedia options. It seems to me an easy way to avoid many issues.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,152
Rep:
Quote:
Originally Posted by enorbet
....many of Digikam's dependencies are also needed for other important multimedia options. It seems to me an easy way to avoid many issues.
Agreed. For that reason alone it should be included.
At one time the plug-ins were a separate package, but that hasn't been the case for quite a while.
As I don't use digiKam, it angers me to no end that I'm forced to build and install it just to have the plug-ins available in Gwenview.
digiKam is a time consuming build and the last version to build successfully on this box was 3.5.0. I haven't tried it recently, but as all I need are the plug-ins, 3.5.0 will do.
digiKam is a time consuming build and the last version to build successfully on this box was 3.5.0. I haven't tried it recently, but as all I need are the plug-ins, 3.5.0 will do.
Strange, the latest on slackbuilds.org is 4.14.0, and it seems to build fine here.
Hopefully not reading all 35 pages won't have been too lazy on my part and if someone mentioned it this will just be an additional vote. Why oh why is Digikam not included in the Recommended KDE-based full install? Almsot everyone has a digital camera and many of Digikam's dependencies are also needed for other important multimedia options. It seems to me an easy way to avoid many issues.
That's from user's point of view. From maintainer's point of view, adding so many new packages just to satisfy one package is overkill.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,152
Rep:
Quote:
Originally Posted by drgibbon
Strange, the latest on slackbuilds.org is 4.14.0, and it seems to build fine here.
Well, fine, but it doesn't build here. In fact, as I never use digiKam I just tried to start it and it returned an error that it can't find libopencv...whatever, and, yes, opencv is installed.
Doesn't matter as I only need the plug-ins for Gwenview and those work.
That's from user's point of view. From maintainer's point of view, adding so many new packages just to satisfy one package is overkill.
I truly don't understand the usage of "overkill" in this instance since Slackware walks a neat line by solving lots of dependency issues before they even become issues by having them installed (taking up hard drive space -cheap) while services off by default where it applies so as not to use up valuable computing resources (expensive). The Recommended Full Install is tied to KDE and Digikam is an important KDE app that shares many dependencies with other apps. Given the Slackware philosophy, and the fact that SlackBuilds exist, exactly why is this a big deal for maintainers?
Willy is talking about the maintainer of Slackware itself; Pat. A Slackware that keeps growing in size, creates an ever increasing maintenance burden. It has to stay manageable.
And Digikam does not have a history of being easily maintainable. Also, its dependency opencv is a huge festering ball of code. There's also the Slackware DVD which has to be taken care of - it has finite capacity for storage.
Willy is talking about the maintainer of Slackware itself; Pat. A Slackware that keeps growing in size, creates an ever increasing maintenance burden. It has to stay manageable.
And Digikam does not have a history of being easily maintainable. Also, its dependency opencv is a huge festering ball of code. There's also the Slackware DVD which has to be taken care of - it has finite capacity for storage.
Yes, i'm talking about Pat's burden; sorry if it's not clear on my original comment.
I'm the maintainer of digiKam in SBo and like AlienBOB said, it's not that easy to maintain digiKam with all those changes in the deps since it's very closely related. A slight change in one of the deps and you may need to find patches for digiKam
Well, fine, but it doesn't build here. In fact, as I never use digiKam I just tried to start it and it returned an error that it can't find libopencv...whatever, and, yes, opencv is installed.
Doesn't matter as I only need the plug-ins for Gwenview and those work.
how did you build it?
i built it many many times with the slackbuild script available in SBo and it works fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.