[Slackbuilds-users] Clarification of REQUIRES and dependencies
Ryan P.C. McQuen
ryan.q at linux.com
Fri Nov 28 17:39:05 UTC 2014
Here's what I do when I'm installing something with a lot of
dependencies. I ctrl + click each dependency (on SBo), then ctrl +
click each subsequent dependency. When there are no dependencies left,
I start at my right-most browser tab and feed a long string of
packages to sbopkg. So for inkscape, I end up with something like
sbopkg -i libsigc++ -i glibmm -i cairomm -i pangomm -i atkmm -i
mm-common -i gtkmm -i gsl -i numpy -i BeautifulSoup -i lxml -i
Works every time! If dependencies were listed in multiple places for
packages, this process would almost certainly be more frustrating, and
I would end up with a lot of redundancy.
I agree with Willy's interpretation on this.
On Thu, Nov 27, 2014 at 4:18 PM, King Beowulf <kingbeowulf at gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 11/27/2014 01:13 AM, Kyle Guinn wrote:
>> Willy and I have a disagreement about this line of
>> "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,
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
> -----END PGP SIGNATURE-----
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
More information about the SlackBuilds-users