[Slackbuilds-users] Clarification of REQUIRES and dependencies

David Spencer baildon.research at googlemail.com
Fri Nov 28 19:42:40 UTC 2014

> Here's what I do when I'm installing something with a lot of
> dependencies.

I used to do exactly what you do, Ryan; it's a good methodology, but
life's too short to do that for hundreds of packages. So I wrote
something better. Inkscape is for wimps: here's what I do to install

slackrepo build --install thunar-sendto-clamtk

And here's what I do to build the *whole* repo.

slackrepo build

That's all.  It takes three days but it *works*.  And here's what I do
to update the *whole* repo, after every public release.

slackrepo update

That's all.  It works (overnight ;-).  All rebuilds automatically
taken care of, no broken shared libs.  But this new interpretation
*breaks* *that* *forever*.  Why?  Where is the advantage?  Could
someone explain *Why* please?

The more I think about this, I really get quite upset.  It even breaks
*manual* updates, Ed, because you have no way of knowing for sure
whether your existing package was broken by an update for an
*unlisted* level one dependency. Nobody supporting this interpretation
has addressed what to do about optional deps or updates, except to
explain how you all like doing stuff manually.  <troll> Well, if you
all enjoy unnecessary work, a bit more would be good, right? </troll>

Just because sbopkg can't do better, please do not break second
generation tools like slackrepo that go far beyond sbopkg and sqf.  If
you go through with this interpretation, I might as well give up
developing it.

If a package has a direct dependency, put it in REQUIRES.  It's
simple.  It's robust when dependencies of dependencies change.
Please, what is the *problem* with that?  What does it *break*?

Sorry for the rant and thanks for listening.

More information about the SlackBuilds-users mailing list