GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
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.
I would assume that Slackware developers have this information regarding the package(s) they are maintaining, so theoretically adding said information to some file somewhere should be a relatively easy task. Surely easier than it would be for a regular user to do so.
FWIW, I agree. For anyone who would like to have this information, such a file would be great. It'd be a rather large file, but that's OK..
PS - What I'm doing now: thinking about building Cairo-Dock, to see if I like it.. . That should keep me on my toes, dependency-wise! Though by now, with any luck, I have all its deps; it's a pretty small app so hopefully it won't want much.
Last edited by GrapefruiTgirl; 02-05-2010 at 12:38 PM.
Playing the troll card even though I wasn't trolling is exactly what a troll would do.
--
Perhaps I have not been clear.
I am not asking why the Slackware developers do not modify the package management utilities so that they have automatic dependency resolution. I understand that various Slackware users prefer it as such. What I am asking is why the Slackware developers do not provide dependency information, either in a global file, or, in a local, per-package, file. As an example, the developer(s) who are "in charge" of maintaining the vim package, surely already know(s) what other packages it depends on. So said developer(s) could list said dependencies either in a global file, or in a file included in the vim tarball.
And I was stating that this task would surely be easier for said developer(s) than it would be for a regular user.
A global file would have various advantages. Minimalistic Slackware installations would no longer be a PITA. Also, (to me) it makes sense. These are official Slackware packages we are talking about.. so if you're sticking to the official Slackware package for some piece of software, surely you are sticking to the associated dependencies. Why not provide the file?
Last edited by carbonfiber; 02-05-2010 at 12:47 PM.
now now brianL you know very well the question is that old one the answer to which is 6 x 9 being equal to 42 and by the way the diodes in my left side are hurting ... on the other hand the question may be: Why is there a fifth book in The Hitchhikers Guide to the Galaxy Triolgy?
I'm not desperate. I've been doing you the courtesy of replying to your posts. It seems you were unable to comprehend my original post on this matter. Also, I was not asking you; originally, I was not asking anybody. The title of the thread is "What are you doing now?".
Last edited by carbonfiber; 02-05-2010 at 02:01 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.