Why does patrick seem to favor slackpkg over swaret?
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.
Why does patrick seem to favor slackpkg over swaret?
I was just wondering if anybody had an idea as to why slackware distibutes slackpkg in /extra but not swaret? I use swaret, but have never used slackpkg.
I'm not interested in flaming or pkg managers are dumb or anything like that. They seem to both have the same puprose--do they both behave the same way? Thanks in advance for any insight.
afaik swaret has not released source code. There was also some nasty accusations against slapt-get coming out of the swaret camp. The maintainer of swaret has since been persona non grata on freshmeat. That's the last I heard of it, anyway. It was said at the time that slapt-get had a future, and that swaret's was dubious.
Ive had no problem with slackpkg, since switching over from swaret.
Had too many dep.'s on swaret. Im a happy slackpkg 7 months now, havent had ne problem usin it on slackware--current. Plus i say, DOnt knock it an till you try.
Why does patrick seem to favor slackpkg over swaret?
And odd thing to ask the general public ... wouldn't
it make more sense to ask pat that? :)
Unless someone has an actual quote (e.g. from
a mailing-list or newsgroup) all you'll get is speculation,
and if it's quotable you may have just as well
found it using google.
I heard that at one point swaret was going to be included in Slackware or was actually included but was removed to to the behaviour of one of the swaret developers.
According to the website thought, Swaret 2 will be written in Perl.
According to a review on distrowatch, the author states that slackpkg does not look at dependencies, it just installs the requested package. THat was written in December 03, and version 1.3 was released on Nov 1 this year. Does anybody know whether or not slackpkg deals with dependencies now? (i ask because I couldn't find any docs on it)
Cybermonkey: Please read the first post--I don't care what you think about the package managers--I just wanted to see if people new why slackware would favor one over the other.
No, Slackpkg doesn't do any dependency tracking. Slackpkg just downloads and installs the requested package/packages. Personaly, Dependency tracking is annoying. When your just upgrading slackware its pretty much useless.
Last edited by predator.hawk; 11-10-2004 at 07:30 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.