how do you keep up with slackware-current?
 

quick question: how do you keep up with slackware-current? Do you download the packages and run upgradepkg or something else?

Yes, or use a program that will do that automatically for you.

Search these threads for either swaret, or slapt-get

http://www.linuxquestions.org/questi...82#post1614982
http://www.linuxquestions.org/questi...ghlight=swaret

http://www.linuxquestions.org/questi...der=descending

Lots of people use Swaret . There is also a GUI called QtSwaret

Or just rsync, read changelong, and then installpkg.

I don't like swaret or apt-get at all.

Awesome. I only knew about swaret so you even informed others along with the creator :)

Also to those who hate GUIs and prefer the console. Its not like I don't use the console I just prefer a GUI when possible cause you can work faster with them usually. Its hard to benchmark that sort of thing ;-)

you left out the best one, well sorta, sombody mentioned apt-get but what he really meant was slapt-get. If I were you I wouldnt touch swaret with a 10-foot pole. Unlike the other 3rd party package managers, slapt-get has actually been adopted as the official manager for Vectorlinux which is basically a mepis-like distro but based on slackware instead of debian.

Oh and there is also a GUI for slapt-get called Gslapt, but I cant comment on that since ive never had the need to use it, I perfer CLI for my package management.

Why doesn't anyone mention slackpkg ? (in /extra)

Does slapt-get actually have automatic package updating? or do i have to manually update each and every package in my Slack?

EDIT:
Swaret is good, it all depends on how you use the updaters, and if you know wtf you're doing.. I could comment on slapt-get the same way they did on swaret a few posts back and say it'll destroy my system and ruin my kernel, but that's because i dont know how to use it..

Stick to what you like..

edit: thanks SiegeX, i meant to say slapt-get. fixed

elyk,

Regardless of how you choose to update, make sure you *read* the ChangeLog - Slackware is not designed to be blindly upgraded; issues will crop up with upgrades, and Pat makes these clear in the ChangeLog (e.g. the change from X.Org 6.7 to 6.8 caused a lot of keyboard trouble with people who upgraded and didn't bother to read the ChangeLog) and may offer advice on how to deal with these.

Perhaps because slackpkg, while useful for tracking current or installing official patches, is useful ONLY for doing that. Whereas other tools can do that and more, e.g. download from unofficial repositories, perform some kind of dependency resolution, etc.

[n] how about Qtswaret with Proxy?
 

Hi,
I tried with global 'http_proxy=", etc. env variables but can't connect to web using Qtswaret....
I am behind proxy that requires authentication...
Any idea?

Thanks.
Nirav

Fortunatly I wrote a fairly decent bash script called slapt_update which does this (also listed in the slapt-get FAQ). If you put it in your /etc/cron.daily folder then every night at ~4am it will run to see if there are any new packages for you to update, if so it ill email you letting you know and include a list of packages to be removed,upgraded,installed. Note that the removed part only pertains if you are tracking current. It also has the option to send the data to STDOUT incase you wanted to pipe it elsewhere, and if you have a cellphone you can just put the email address of your cell phone and it will send you a text message ;). I don't allow the script to automatically install the packages for you as thats generally a bad idea, but it does have the options to download the files so that they are already there when it comes time to install, and a simple slapt-get --upgrade should do the trick.

"Perhaps because slackpkg, while useful for tracking current or installing official patches, is useful ONLY for doing that. Whereas other tools can do that and more, e.g. download from unofficial repositories, perform some kind of dependency resolution, etc."

Well said, and id also like to mention that for official packages I find the slapt-get interface a bit more intuitive, but that part is objective.

Good call and extremely important, this reason if often where the FUD about slapt-get breaking boxes stems from.

I would have to disagree with you when talking about *official* packages, and that designation is important. Many people don't know that for official packages slapt-get doesnt do any dependancy resolution at all, which is a good thing as there is zero dependancy data for official slackware packages. For official slackware packages slapt-get is merely just a nice automated front end to pkgtools, and AFAIK you *shouldn't* be able to b0rk your box via installing *official* packages with the caveat of reading the changelog of course. For 3rd party packages, slapt-get has its own dependancy metadata format and many packages (and all the ones on vectorlinux) use this. But when dealing with 3rd party packages you are at the mercy of the packager and there are no guarantees.

Instead of just waving my hands and saying "swaret is bad (tm)" Ill repost something I put in another thread about 2months ago regarding why I believe this to be so.

I use slap-get.. seems to work pretty well for me.. haven't had any trouble yet.. however, I do have a question for others using slapt-get to stay current..

I was using slapt-get --upgrade to stay current.. but I read in another thread that you should run something like slapt-get -distro --upgrade or something along that line... I couldn't quite figure out what the difference was..

yes, when tracking -current you should run 'slapt-get --dist-upgrade' (my script does this btw to determine packages if you say yes to tracking -current). From the man page:

I highly suggest you read the slapt-get FAQ , its probably one of the better ones ive seen, chalk full of usefull info.

SiegeX,
hmm...sounds like slapt-get does by default
what i have been configuring swaret to do.
(minus your dep issue) Additionally, the script
you speak of sounds very nice.

I'm sold...will try to transition over in the near future.

What exactly do you mean by "unofficial repository's" you mean like "not a standard mirror".

But the question was "how do you keep up with slackware-current"

I install slackpkg, choose a mirror near me that points to the slackware-current directory on a mirrored server, and i tell slackpkg to upgrade all my packages. (or choose them seperatly).

It's SOO easy, and it does JUST what the question says: "keep up with slackware-current"

Curious, u saying Swaret's attempt at dependency checking is worse than not having it at all, notwithstanding the deck of cards Slackware deals?

Great, let us all know what you think once you switch over, whether it be good or bad.

I should also mention that even if you don't use my script, slapt-get already does automatic updating in so far as to say a simple 'slapt-get --update && slapt-get --upgrade' will grab all the new packages for you and install them. All my script does is run the updating for you while you sleep, parse out the data that slapt-get returns and formats it in a nice email for you (and optionally download the packages). This way you dont have to constantly check the changelogs every day

Absolutly, because official Slackware packages have NO dependancy information AT ALL, zip, zero, nada. Swaret attempts to get around this via 'ldd' and well you can just read the reasons I mentioned above why this is a bad idea. If you want dependancy resolution, then do it right and actually include dependancy meta-data in the packages, and as I mentioned, this is exactly what Vectorlinux did to all of the slackware packages they include in their distro. IMHO this is the only approach I would trust my box with.

By "unofficial repository" most people are referring to linuxpackages.net, although their are probably more than that one out there, but thats the major one. Although you're correct, slackpkg does "keep up with slackware-current" just fine, why limit yourself? Slapt-get does both, and IMHO in much nicer interface, afterall its coded to match apt-get's abilities.

P.S.

slackpkg doesn't have my script :D

My personal opinion is that all the package update tools are just those, tools. As in, if you don't know how to use a hammer and you hurt yourself with it, then it's your fault, not the hammer's. Same goes for swaret, slapt-get, or whatever.

That being said, /any/ tool should be used with a big measure of caution.

I've summarized my opinion on this subject along with they way I use swaret on my blog, I won't repeat it here. However, if you choose to read it feel free to substitute all occurrences of "swaret" with any other update tool name. It can be found at http://rignesnet.tzo.com/archives/20...T22_32_20.html

No arguments there, but using the same analogy, not all tools are created equal. I see swaret as a hammer with a broken handle that may or might not snap off at any given moment, and slapt-get (and even slack-pkg) as a sturdy rock-solid hammer.


Oh and BTW I read your blog and ive lost all faith in ##slackware for many reasons, but the situtation you described is definetly one of them. I don't agree that swaret is the best tool for the job, but I full heartedly agree with your statements in general.

well, i'm having a problem with the script...
but slapt-get itself seems to work. i went ahead and used
swaret for this update though, because i already have my excludes
defined and wanted to authorize all the packages individually.

i have edited the script and it is executable,
but it doesn't seem to do anything. no mail.
nothing in the maillog. anyways, i'm trying to follow
the code to see what is going on...

May I ask what specifically about swaret makes you think of it as the broken handled hammer? And what about the other tools makes them better in your eyes? As I've said, I've only used swaret and haven't tried anything else because I've personally had only excellent results with swaret. But that doesn't mean I'm mindlessly stuck on it.

I'm always up for a better tool to make my life easier.

PS. I assume your main problem is the dependency checking? Or do you have other issues. I'll look back on the thread quick and review your comments on why ldd is bad.

hmm...just tried the other script [update-notifier]
and it works like a charm. sorry i couldn't give you
any feedback on what the problem was, SiegeX.

Actually, there was no problem, my script is working correctly. You see its job is to notify you when new packages are available. Since you just installed it, and since slackware hasnt released any changes to -current since then, you shouldn't get any email. If you want to force it to send you an email to ensure yourself that it really does work, just edit the date in the /etc/slapt-get/changelog.last file. It doesn't matter what date you change it to as long as its different than what it originally said. Once you save it, re-run my script and you should notice an email in your inbox.

Just to let you know, the entire reason why I wrote my script was because the update-notifier script is totally fubar when tracking -current. It will send you an email every day claiming new packages are available even when thats obviously not true. I emailed the author about this problem over a year ago and he said he had no intensions on making it work for -current. Mine works with both stable and -current.

Yes, this is my only problem with swaret, and I consider it a big one because thats swaret's defining feature if you can call it that.

Let me just make it clear that I have no problem with dependancy checking whatsoever, what I do have a problem with is trying to force it upon a system that was not made for it.

I prefer slapt-get over slackpkg and swaret because slapt-get...[list=1][*]Understands *official* packages weren't made with dependancy meta-data and honors that.[*]Has its own dependancy meta-data scheme which has been highly adopted, including an entire distro[*]Works with non-official repositories (ie linuxpackages.net)[*]is modled after apt-get, a tried and true program[*]is under constant development[*]The author is very open to suggestions and often includes the good ones in new releases (ive had two thus far)[*]The author can be reached on IRC in the #slapt-get channel on freenode[/list=1]

Is it just me, or is it impossible for this forum to go much over 2 weeks without this thread being repeated.

there were a couple packages that i hadn't updated yet...
or are you saying that is doesn't check the packages,
but rather the date of the changelog?

went ahead and did an update with slapt-get...
it did catch a package that swaret hadn't updated in ages.

i did notice that the update-notifier uses the --ignore-excludes flag...
but i don't mind getting an email everyday.

also, i tried the --simulate --dist-upgrade options...
i don't like that at all...it insists on uninstalling packages
i have compiled myself as well as re-installing packages
i have uninstalled.

i do wish slapt-get did individual authorization for each update as swaret does,
but otherwise i'm pretty happy with it.

This is exactly correct, and in fact *both* my script and the other do it this way. The only reason why you got an email from the other script and not mine is because it's broken trying to use it for current, and the author has admitted as such. Here is a small excerpt from our discussion about 8months ago

There are actually two problems here, and both are easily fixable. If you want it to ignore custom packages you made yourself, then simply put an identifier on each of the package names and put that identifier in your EXCLUDE list. For example I use checkinstall to make all my custom packages and so I use the '--pkgrelease checkinstall' option which adds the word 'checkinstall' to all of my packages.

If it is trying to upgrade unofficial packages with official packages and you don't want that behavior, then you're in luck because this is one of the features I suggested to the author of slapt-get and it was added in the latest version. Read THIS POST

If you are not fully tracking -current, that is to say you have removed certain packages then use plain old '--upgrade' instead of '--dist-upgrade'. And it wont try to install packages that already have been removed.

Not related to which tool to use, but for those of you that use slackpkg - how do you get it to upgrade everything that you have installed that has an update available?

For example, if I want to update xine-lib, I type
and it does what needs doing.

Is there a simple one-liner that will tell slackpkg to look at my /var/log/packages (or whatever) and update everything that's updatable?

you can update by folder...such as:

slackpkg upgrade a

and it will let you know of all packages in "a" that are available for upgrading...it also works for extra, too.

it lists available updates, and you can choose to have it update them, or you can cancel out and just update the ones you wish to.

If your tracking Slackware current use slackpkg upgrade slackware to upgrade all installed packages (that would be in the slackware directory) Use slackpkg upgrade extra to upgrade packages that are in the extra directory.
If you track a stable release( EG 10.1) you would use slackpkg upgrade patches because updated packages are kept in the patches directory

Thanks for this. It's exactly what I was looking for. I had already upgraded everything by going through the disk sets (a through xap), but didn't realize you could do the same with the whole slackware directory.