[Slackbuilds-users] Clarification of REQUIRES and dependencies

King Beowulf kingbeowulf at gmail.com
Fri Nov 28 00:18:07 UTC 2014

Hash: SHA1

On 11/27/2014 01:13 AM, Kyle Guinn wrote:
> Willy and I have a disagreement about this line of 
> http://slackbuilds.org/guidelines/
> "The content of REQUIRES should only be first level dependencies
> (i.e. no deps of deps)."
> The disagreement occurs when package 1 depends on packages 2 and
> 3, and package 2 depends on 3.  Should 3 be listed in 1's
> -----------------?
> I'd love to hear other opinions and use cases. -Kyle

IMHO, we need to keep things simple.  I use a pad of paper to create a
dependency tree. Often, this tree is simple (qemu, stellarium), at
other times complex (inkscape, vlc). To whit,
1. create branch of direct listed deps
(1a. create branch of any optional deps that may be useful)
2. Look up each dep on SBo and create a dep branch
(2a. already installed? Done.)
3. repeat until deps tree is complete with dotted lines for overlaps
4. build and install one at a time along each branch

(OMG! It took me an HOUR to install this package!)

How often and how many times would a typical user install and update
SBo packages?  I play with A LOT and the time sink is not so great
that I crave automagical dendency mumbo jumbo.  Security is not an
issue.  Most packages I use regularly don't get updated unless there
is a serious bug that bites me, a new functionality, or a new
Slackware install.

Seriously, the beauty of Slackware is that we can maintain it anyway
we see fit, write scripts to automate many repetitive tasks (thanks
Alien Bob!), use slackpg (thanks Piter Punk!), slackpkg+ (thanks
zerouno!) and sbopkg (meh...not my cup of tea...); or we can go old
school and do it all manually.

But lets not go crazy and list every possible deps or deps umteen
layes deep in every README or REQUIRES line.  What are we, freakin'
Debian or Ubuntu?

Thanks for reading,

Version: GnuPG v2


More information about the SlackBuilds-users mailing list