-   Slackware (
-   -   Third-party Repositories (

sfxpt 05-18-2008 12:15 AM

Third-party Repositories
Hi everyone:

First of all, I've already done some searches before this question.

For example, there has been a thread discussing which of the third-party repositories is most popular, but I didn't see concurs.

Anyway, it seems to me that is the most popular third-party repository. And my question is how to use it with slapt-get?

I know from

If I am to use the "NYI New York Internet" mirror, I would set
Slapt-get to

But when it comes to practice, I have the following questions.

- Does contains official packages as well?

- If not, do you recommend VectorLinux's repository? Does it have more packages than

- Will setting above find all packages from for me? Or it is only for the very version of Slackware that I choose?

- If I can't find the package that I want in Slackware-12.1, will packages from Slackware-12.0 be OK for me?

- If it is OK, how can I make slapt-get search Slackware-12.1 by default then fall back to Slackware-12.0 when not found?

- more on package finding, while doing random checking of the available packages, the first two packages from, FFmpeg & Firebird, I don't see them in

In this case, would slapt-get search find those 2 packages for me?
If not, what should I do?

All in all, what's the best practice using third-party repositories?

Thanks a lot


sfxpt 05-18-2008 12:21 AM

PS. coming from Debian, I'm more a use-a-package guy than build-my-own-package guy.

I respect your decision to build your own packages, but ...

SqdnGuns 05-18-2008 12:39 AM

Use , better to build them on your own box then use a build from someone else. Be sure to read the FAQ @ slackbuilds.

T3slider 05-18-2008 01:11 AM is a more reliable source than in my opinion. I know nothing about slapt-get or slackpkg, so I can't be more help than that -- I will just say that has some poorly-built packages with questionable dependencies that have the possibility to bork your system. Although there ARE some reputable packagers at, you would have to find out which ones are reputable and only use their packages -- and that's a lot of work, and not very convenient when using slapt-get. has a large repository with well-built packages that all include a SlackBuild so you can see how they built it or compile it yourself using their SlackBuild, if you want.

I trust, Alien Bob's repository ( and rworkman's repository ( 100%, and 50% (though I'm a pessimist and I always just use the SlackBuilds from and not their pre-built packages). If you want huge repositories with every package you could possibly want, Slackware isn't the distro for you -- some packages won't be available anywhere and will need to be compiled (by you) from source. That being said, with the nice repositories listed above, that would be an exception instead of a rule, but just be warned.

sfxpt 05-18-2008 11:11 AM

thanks a lot T3slider, that's really insightful.

anyone else has more experience with slapt-get & third-party repositories?


slackass 05-18-2008 01:54 PM


I also just came from Debian a few months ago. The big reason I came to slack is because I have to have a system that works after a package install. And doesn't break something else during a package install. And is reversible after a bad package install. If you'll just take the time to learn use SlackBuilds & src2pkg, I think you'll be rewarded with just about the most stable system available.

The only ready made packages that I will use is rworkman's, Alien Bob's, & sometimes

It only takes a little while to "roll yer own", and you'll get better results.

All times are GMT -5. The time now is 06:49 PM.