Post your slapt-getrc for slapt-get/gslapt
 

Where do you find Slackware packages?

This is what I have:

WORKINGDIR=/var/slapt-get
EXCLUDE=^kernel-.*,^glibc.*,.*-[0-9]+dl$,^devs$,^udev$,aaa_elflibs,x86_64
#DISABLED=ftp://ftp.sunet.se/pub/Linux/distributions/slackware/slackware-current/:OFFICIAL
#DISABLED=ftp://ftp.sunet.se/pub/Linux/distributions/slackware/slackware-12.1/:OFFICIAL
#DISABLED=ftp://ftp.slackware.com/pub/slackware/slackware-12.2/:OFFICIAL
#DISABLED=http://software.jaos.org/slackpacks/12.2/:OFFICIAL
SOURCE=http://slackware.mirrors.tds.net/pub/slackware/slackware-12.2/
#DISABLED=http://scxd.info/pub/
#DISABLED=http://slackware.sukkology.net/repository
#DISABLED=http://linuxpackages.inode.at/Slackware/Slackware-12.2/
#DISABLED=http://repository.slacky.eu/slackware-12.2/
#DISABLED=http://rlworkman.net/pkgs/12.2/
#DISABLED=http://www.slackers.it/repository/
#DISABLED=http://www.slackware.com/~alien/slackbuilds/

There are only a few places I'll get Slackware packages. I download security updates from the Slackware mirrors. I download trusted Slackware packages from Robby and Eric. I download, install software using the build scripts from slackbuilds.org. I use src2pkg to install source.
Under no circumstances will I install anything from linuxpackages.net as their software is $hit.

Slackbuilds.org should always be your first port of call. Their slackbuilds have never failed for me. You can use sbopkg to automate the compiling and install of programs from slackbuilds.org:
http://sbopkg.org/
The slackbuilds from rworkman's and alien_bob's repos are very good also.

I've read a few negative things about slapt-get, so I've never used it. Slackpkg, sbopkg, and src2pkg, work for me.

Yeah, I never use slapt-get.

So there are no other trustworthy Slackware repos?

Well someone may list one that they consider trustworthy.
Robby and Eric are two Slackware developers and their software always functions very well indeed (see my signature for links). Slackbuilds.org has exceptional quality control; the slackware packages that their build scripts create always work flawlessly for me. gnashley's src2pkg utility takes vanilla source code and creates solid Slackware packages. The Slackware mirrors are the only sites to go to for security updates.
I don't need any other sites.

SlackBuilds.org currently has (exactly) 1600 build scripts on it (according to my local mirror). That's my primary source of packages. If they're not on there, I will try and write a script myself and submit it so that someone else doesn't have to go through the trouble of doing it. Maintaining a package on SlackBuilds.org is almost no effort, and just requires replying to the odd email about a particular package.

Obviously, if you're like ppr:kut, who maintains 123 packages on SlackBuilds.org, or Erik Hanson with 102, I imagine the workload increases somewhat!

edit: I made a graph!

Disclaimer: this is how I got the stats:Ran that from my local SBo repository.

+1 for slackbuilds.org and also Robby's and AlienBob's repos.

If slackbuilds doesn't have it, I also make a build script and submit it.

src2pkg is ok, but I only use it for quick tests to see if a package has a straight-forward build, before I make a script.

Really you should avoid *any* prebuilt packages except those I listed above in my opinion. There is no quality control of any sort at linuxpackages.net as far as I recall, and probably the same at slacky. Yes, people have had problems with lp.net packages (including a rootkit in one if I recall correctly).

Using a slackbuild script from SBo is the safest option and you will usually get some support in #slackbuilds on irc.freenode.net as well. The maintainer is always listed in the .info along with email.

sbopkg is a very nice app and can be downloaded from sbopkg.org with support in #sbopkg.

Just curious, what are your guys' opinions on swaret?

And if one uses only the official ftp.slackware.com repo with slapt-get, what could be the risk?

I recently migrated from Gentoo to Slackware as I was getting sick of trying to maintain a gentoo system, but I thought emerge was a pretty solid package manager. I have so far built most packages on my Slackware install by untarring and manually compiling the source code, but this is becoming tedious.

No sir I don't like it, don't like it at all.

Well if you are only using the official slackware mirror then use the official Slackware tool "slackpkg".

Try sbopkg, it will remove much of the tedium involved.

Thanks. I had heard bad things about both slapt-get and swaret. I have used slapt-get twice to install a few things that for some reason, were not manually installing properly (libdvdread and some gnome app i dont recall)

What exactly makes them such horrible applications though?

I did notice after the second use of slapt-get, I had to fix a few things by linking some libraries (sloppy I know)...

I'll try out sbopkg, it looks at least similar to using slackbuilds which has worked out well (apart from having to do a lot of editing on the virtualbox slackbuild to get it to compile)

I know the words "dependency resolution" are looked at unfavorably, but for non-integral applications, and for the sake of saving some time, it can be pretty handy.

one other question on this topic.

Is there any utility for keeping on top of security updates?

I have grown weary of updating my entire system daily, but i don't think i want to fall behind on anything crucial

Just like a script that can read any security announcements that i could run to display a list of important updates?

as opposed to subscribing to a mailing list or reading through the changelogs

I know i am asking too much...

I've found Sbopkg to be excellent,and I use RW and A-Bob's stuff....I've installed a couple of things from Slacky.eu like Exaile without problem....I'm fairly new to Slackware, and it doesn't take long to find all this out for yourself :-) I'm on my third install, clean, with a studiously recompiled kernel, VB is running with usb support for my vertical market programs...even my Dell keyboard layout, i.e. dedicated keys are working, it all works, and it runs quite frankly like a raped ape ;)

Nevermind. Misread the question.

But, really it is good to subscribe to the slackware security mailing list.