Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 02-07-2005, 08:48 AM   #16
Registered: Mar 2004
Location: Minneapolis, MN
Distribution: Slackware 10.1
Posts: 93

Rep: Reputation: 15

It's hilarious how people blame swaret for so much. In a nutshell it just downloads a package, runs removepkg on the old one, and installpkg on the new one. Upgrading by hand isn't any safer, the problem comes when people upgrade something they shouldn't be upgrading. You can manually break a computer as easily as you can automatically do it, heh.

The fact that Pat doesn't "support" it means nothing, so that can't really be used as a negative against swaret. Pat hardly ever supports anything slack-based that he didn't make. Tons of people use Dropline GNOME, and he won't even consider simply putting the installer in /extras (which kind of irks me, considering how hard those people work to keep GNOME current and functional, but that's a different discussion). I love Slackware and think Pat does an excellent job, but I certainly have come to learn that hearing he doesn't like something is no reason to think of it as bad.

Of course, I don't run Slackware for servers.

Glad to hear you're sticking with Slackware.
Old 02-07-2005, 12:29 PM   #17
Senior Member
Registered: Sep 2003
Location: Indiana
Distribution: Slackware-current
Posts: 1,257

Rep: Reputation: 48
I think your first paragraph sort of misses the point. If you are doing it by hand that probably means you read the changelog. Then you are more likely to have read the kbd note, that some package should be removed, another is a new package that needs to be installed. Whereas if you run swaret, that isn't necessarily the case. I agree that swaret/slapt-get can both work for someone if they use it properly.

Pat did put swaret in extra for awhile, but the developer at that time was such a loose cannon that he did not want to be associated with him, IIRC. As to dropline, as long as they include PAM it seems clear that Pat will avoid being seen as sanctioning them as part of the distro or any sort of approval.

I do agree with you to some extent. Just because Pat doesn't include something that doesn't mean you shouldn't use it, its your box. I think in some situations though you might want to consider why he doesn't include it.
Old 02-07-2005, 01:56 PM   #18
Registered: Mar 2004
Location: Minneapolis, MN
Distribution: Slackware 10.1
Posts: 93

Rep: Reputation: 15
No, I understand the point that if you're updating by hand, then you probably know why you're updating. My comment was more or less directed at all the negative opinions about swaret "breaking" people's computers, or being a faulty piece of software. It's basically just a frontend script for normal Slackware package management. Now, I don't go downloading scripts that other people wrote that do things that I don't fully understand, because chances are running random scripts without knowing what I'm doing is going to break something. I don't know why that same logic doesn't apply to swaret (and other Slackware package apps). Instead, people just say they're shitty or "dangerous".

As for the developer being a "loose cannon", I'm not really sure if that applies to his personality, or his coding. Though, the program hasn't changed much in the distant past versions. Swaret basically functions like it always has, so it seems to be more than likely a personality thing. Once again, program gets a bad rep because Pat doesn't "support" it and removed it, etc..etc. For all we know, he didn't like the guy's IRC nick and decided to take it out of /extra (which would be perfectly all right, it's his distro), and now tons of people warn others not to use it because Pat doesn't approve.

Same thing for Dropline, except much more of a shame, IMO. Pat doesn't like PAM. Well, you know, I don't much like it in it's current state, either. However, PAM, HAL, and the 2.6 series kernel are all around to stay, and I see no reason that they all won't achieve the level of stability and solid function that we see in the well-aged 2.4 series and relative utilities. And you know what is going to help that come along? Projects like Dropline GNOME, that work to incorporate those features to a broad range of people willing to test them, thereby giving feedback and helping them improve. I wish they'd get a little love for doing all that hard work. Instead, they get treated like they have some kind of disease, or are somehow beneath other slackers.

Now, I don't believe any of those things should be in normal, run-of-the-mill Slackware. I think it should contain only the tried-and-true. But that's what an /extra directory and a little disclaimer is for.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Where to get Slackware Current? mjjzf Slackware 3 07-09-2005 10:03 AM
how do you keep up with slackware-current? elyk Slackware 33 05-07-2005 11:21 PM
Slackware-current milkycow Slackware 7 03-21-2004 12:21 PM
Slackware Live CD rocks! Must have! Whitehat General 7 08-28-2003 09:48 AM
slackware 8.1 iso vs slackware current illtbagu Slackware 9 02-26-2003 07:10 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:50 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration