[Slackbuilds-users] "Required" package listing in .info ?

Deak, Ferenc ferenc.deak at gmail.com
Mon Oct 18 09:59:16 UTC 2010

First, if you use sbopkg, it supports queue files (for dependencies), and an
sbopkg co-developer Mauro Giachero has created a repository of
sbopkg queuefiles.
See http://sbopkg.org/queues.php,
You can find queue files for all the packages.

Second, I have similar opinion as yours. But I understand that sometimes
there are many choices for satisfying the dependencies of a package, and
it is good that (under slackware) we are free to do that without fighting
with a package manager.
So I would not call it dependency or I would not call it required packages,
but I would call it default build environment or tested build/working
environment (or even suggested environment)
 - in which the packager and the sbo maintainers tested the package,
   and perhaps the packager *use* the package daily
 - in which I can expect clean build and correct working
 - and has a reasonable feature set for the average user

In my opinion it would be nice if we have an exact (machine readable) list
of this environment, not just a part of a sentence somewhere in the readme

For me as a packager having about ten packages it is not much work,
to create one more line in the .info file, for correctness.

And perhaps it would help the sbo maintainers (but i'm not a maintainer!)
to easily create the same environment as the packager had when he/she built
the package.

But on the other hand, if you don't build every package in a clean slackware
and only the "required" packages installed, you cannot expect the same
result as the the packager had, because a configure script (and the build
process) can use the extra packages you already have.


More information about the SlackBuilds-users mailing list