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.
Distribution: Slack/Ubuntu & OpenBSD (not a linux distro)
Posts: 56
Rep:
i just got rid of swaret and installed slapt-get, XBONE is a big time looser !! i had this kid on my jabber list for a while, i was so tired of his behaviour... man why some people who can scripty a little bit are like that ??? but yeah hoop de development of slapt-get is much better....
I think you may be jumping the gun. Swaret is not dead. Xbone has been removed from the development team some time ago. And the swaret site is back up at swaret.sf.net.
I wouldn't let a developer who isn't even part of the team anymore effect which one you use. Of course, if you like slapt-get better than swaret then by all means, use it.
Distribution: Slack/Ubuntu & OpenBSD (not a linux distro)
Posts: 56
Rep:
Re: Don't Jump the Gun
Quote:
Originally posted by rignes I think you may be jumping the gun. Swaret is not dead. Xbone has been removed from the development team some time ago. And the swaret site is back up at swaret.sf.net.
I wouldn't let a developer who isn't even part of the team anymore effect which one you use. Of course, if you like slapt-get better than swaret then by all means, use it.
Brian
What i really don't get is, this XBONE looser was the fouder of this project ? or do i'm wrong ? how is possible he is not a part of his own project anymore ? who is taking this over ? serius people ? i use to like swaret but when a developer behave his self like that i don't trust the software he is working on. (got my point of viewt) how can we trust this new development team ? what happend actually with all this swaret thing ?
All I know is that the current project owner is linuxsneaker. He's replied to the effect that swaret is still alive and kicking. And he put the swaret website back up when he said he would. Now, as far as who this xbone was and what part he played in the founding of swaret is I really don't know. My point, don't go on speculation and political crap.
Go on the merits of both programs. And if you really want to know what the internal problems were try going to sf.net and e-mailing linuxsneaker. Maybe he'll replay.
Do whatever you want, but my personal wisdom isn't to condemn the entire project because of one bad egg.
All I know is that the current project owner is linuxsneaker. He's replied to the effect that swaret is still alive and kicking. And he put the swaret website back up when he said he would. Now, as far as who this xbone was and what part he played in the founding of swaret is I really don't know. My point, don't go on speculation and political crap.
Go on the merits of both programs. And if you really want to know what the internal problems were try going to sf.net and e-mailing linuxsneaker. Maybe he'll replay.
Do whatever you want, but my personal wisdom isn't to condemn the entire project because of one bad egg.
Brian
Good post, I for one am tired of the bashing of the project, it's a good piece of software.
It is good, I use it without problem, and will continue.
Question for Swaret users:
is it common to uncomment the linuxpackages source, or is that a cause of problems?
(slack10)
It's no problem to use the LinuxPackages or any other repository, or even several repositories.
Oh well, I can think of one problem. Do not use the -a option when upgrading from something else than an official Slack mirror, for instance LinuxPackages. It you use the -a, most of the installed packages on your computer will be "upgraded" (rather, exchanged) to the ones at for instance LinuxPackages, with perhaps the only difference being that the packages have slightly different compiler flags (usually i486 <-> i686).
That's not necessarily a bad thing, but if you want to keep your box as "Slack-clean" as possible, then it is an issue. When I upgrade I try to keep repository consistent as much as possible, meaning that if a package has been installed from the official tree, then I should take the upgrades of that package from that tree as well, but if it comes from a third-party repository I don't care (even though I try to upgrade "towards" the official tree).
So, anyway, it is no problem to install from third-party repositories using swaret, but be careful with the -a switch!
I've used swaret for a few months now with no problems.
However after reading all this I will start using something else. I refuse to be associated with the asshattish behavior displayed by these people. Open source does not need this sort of idiocy.
given that the person who caused all the probs is no longer involved with the development of swaret, are you not just cutting off ur nose to spite ur face??
Originally posted by joe83 I've used swaret for a few months now with no problems.
However after reading all this I will start using something else. I refuse to be associated with the asshattish behavior displayed by these people. Open source does not need this sort of idiocy.
Given the fact that the developer in question (xbone) is no longer associated with the project why should you have a problem with swaret? If you prefer another program then use it but don't abandon a project because of it's past. For that matter please try and not taint others opinion for a project by making thier past mistakes sound like current ones, this has not been an issue for quite a while.
Note: I do not use swaret, or any other similar program, but don't deny their usefulness to some.
Originally posted by KMcD given that the person who caused all the probs is no longer involved with the development of swaret, are you not just cutting off ur nose to spite ur face??
Not really. I'm not one of those "bleeding edge" types that has to have all the latest packages. I only upgrade for security reasons and pkgtool can do that nicely. I used swaret because it made this process a little simler, so it's not that important. As far as" the person who allegedly caused all the problems being gone" reminds me of someone closing the barn door after the horse is gone. I find it hard to beleive that one person could cause that much ruckus without at least tacit approval of others.
Originally posted by Mephisto Given the fact that the developer in question (xbone) is no longer associated with the project why should you have a problem with swaret? If you prefer another program then use it but don't abandon a project because of it's past. For that matter please try and not taint others opinion for a project by making thier past mistakes sound like current ones, this has not been an issue for quite a while.
Note: I do not use swaret, or any other similar program, but don't deny their usefulness to some.
If I "choose to have a problem " with anything for whatever reason that is my choice. I am curious how I am "tainting people's opinion" or " denying usefulness" to others by expressing my opinion. I come to this site for information, to help, and be helped not to be lectured about what I should/shouldn't have "problems" with.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.