[Slackbuilds-users] the .info file

Leonardo sombriks at gmail.com
Fri Feb 26 01:16:44 UTC 2010

ya don't fork, ;)

it's just and vague idea.

put it on .info file could keep the scripts completely sane (i am not
here to advocate things like "requiredbuilder", these things already
have a place for it) and being optional it never would bother
packagers who don't want us (ordinary users) to have a chance to blow
up our systems, ;)

it's also not dependency tracking, it's meta-dependency tracking.

see a package require others when using some slapt-get still makes me
track what it did on my system, the .info is just a way to site shows
what are called dependencies. And just if the packager (i.e. script
author) wants to put it visible on the site.

i know that some optional stud may evolve, but in the perfect scenary
it will be optional forever.

2010/2/25 Grissiom <chaos.proton at gmail.com>:
> Hi, don't be so hurry~;) I don't think the admins will accept this
> proposal(to add dependency lines in .info) simply because Slackware doesn't
> have it. Users always have an attempt to automate every thing(including me
> sometimes). But in my _own_ view, slackware's philosophy is `program is
> bullsh*t, manage them by yourself`.
> Actually, there is a place to tell user dependencies -- README. However,
> there is even no very-machine-friendly 'format' to declare that. IMHO, it
> force users to read them by their own before making any packages.
> Just my two cents. ;)
> (...)

More information about the SlackBuilds-users mailing list