[Slackbuilds-users] pelican depends on Jinja2 >= 2.7

Kyle Guinn elyk03 at gmail.com
Sat Jan 25 17:53:06 UTC 2014

On 1/25/14, Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:
>> The way I see it, if package A says it needs B and C, then I put them
>> both in REQUIRES.  Whether or not B requires C should have no effect
>> on that.  Maybe some newer version of B won't require C, and then the
>> dependencies for A would be incomplete.
> please have a look on the FAQ
> http://slackbuilds.org/guidelines/
> REQUIRES contains a space-separated list of all required build-time and
> run-time dependencies, each named exactly as listed on the
> SlackBuilds.org site. It should not contain anything that is part of
> Slackware itself. The content of REQURIES should only be first level
> dependences (i.e. no deps of deps).

On the other hand, package A says it depends on B and C, but A only
"needs" C because B needs C.  In this case A is lying and it only
needs B, and REQUIRES should only contain B.  This is the scenario the
FAQ describes.  My first scenario is different.  Which case is this?


More information about the SlackBuilds-users mailing list