![]() |
Slackbuilds intent and philosophy
Hi,
Why does slackbuilds require you to compile the packages from source code? Is there a technical or political reason why slackbuilds (or some other institution) cannot provide precompiled binary packages? This is in response the the slackbuilds FAQ below: Do you provide precompiled packages from your SlackBuild scripts? No. We are not now, nor will we ever be, a source of precompiled packages. The answer doesn't provide a reason, but appears vehemently against it? I don't mind downloading the source and running the scripts to compile, but I would rather not if I can get away with it. Thanks. |
You probably already know this but binary packages have dependencies.
Depending on the system they were built on, they might have "unwanted" dependencies. Providing scripts to do the job is failsafe, and gives absolute control to the one who is building the package. Slackware is about control right? :) Regarding some applications, there might also be licensing issues that prohibit binary distribution (eg. adobe reader) , so a build script is a workaround. |
Also, not distributing binaries exempts them from having to provide the sources from the same site.
|
Saves them on the bandwidth bill as well ;)
|
If you want packages, Alien Bob has many:
http://www.slackware.com/~alien/slackbuilds/ There's also: http://linuxpackages.net/ although I can't really recommend using things off there, as a good percentage fail to work properly for aforementioned reasons. |
Anyway, there's that much crap on TV these days that I'd sooner watch a SlackBuild build. :)
|
Quote:
|
Quote:
|
Quote:
Code:
tr -dc '0-9A-Z' </dev/urandom |
Code:
tr -dc '0-9A-Z' </dev/urandom |
Yes, have a look among the screensavers.
|
cmatrix can be run in a terminal window.
|
| All times are GMT -5. The time now is 05:24 PM. |