Re: [Slackbuilds-users] pelican depends on Jinja2 = 2.7

2014-01-25 Thread Mikko Värri
I see that there are a few ways to look at this. In Python, dependencies are often runtime dependencies. I.e. to build only setuptools is enough. I don't remember if dependency types are defined for REQUIRES. But as you probably already know, I tend to put all direct runtime and buildtime

Re: [Slackbuilds-users] pelican depends on Jinja2 = 2.7

2014-01-25 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I see that there are a few ways to look at this. In Python, dependencies are often runtime dependencies. I.e. to build only setuptools is enough. I don't remember if dependency types are defined for REQUIRES. But as you probably already know, I

Re: [Slackbuilds-users] pelican depends on Jinja2 = 2.7

2014-01-25 Thread Mikko Värri
What is hard-dep? Sorry if this is a stupid question. I don't use any of the tools you mentioned. Is it a non-optional runtime dependency? Willy Sudiarto Raharjo will...@slackbuilds.org kirjoitti: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I see that there are a few ways to look at

Re: [Slackbuilds-users] Issues with newest spotify SlackBuild

2014-01-25 Thread korgman
On 22/01/2014 12:39 μμ, Michael Niemeck wrote: Hi all, (A) Most panels (my suspicion is, it's those that get filled using HTML), basically everything except the top and left-hand menus and the main song list, remain completely blank, Has anyone experienced similar issues? Yes :) Discover,

Re: [Slackbuilds-users] pelican depends on Jinja2 = 2.7

2014-01-25 Thread Kyle Guinn
On 1/25/14, Willy Sudiarto Raharjo will...@slackbuilds.org wrote: only hard-dep and direct dependencies should be listed in REQUIRES since you mentioned markupsafe in the REQUIRES, user must install it first (thus eventually have pysetuptools before installing markupsafe), so it should be

Re: [Slackbuilds-users] pelican depends on Jinja2 = 2.7

2014-01-25 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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

Re: [Slackbuilds-users] pelican depends on Jinja2 = 2.7

2014-01-25 Thread Kyle Guinn
On 1/25/14, Willy Sudiarto Raharjo will...@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

Re: [Slackbuilds-users] pelican depends on Jinja2 = 2.7

2014-01-25 Thread Matteo Bernardini
2014/1/25 Kyle Guinn ely...@gmail.com: On 1/25/14, Willy Sudiarto Raharjo will...@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

Re: [Slackbuilds-users] On dependency definition (Was: pelican depends on Jinja2 = 2.7)

2014-01-25 Thread Mikko Värri
Kyle Guinn ely...@gmail.com wrote: On 1/25/14, Willy Sudiarto Raharjo will...@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

Re: [Slackbuilds-users] On dependency definition (Was: pelican depends on Jinja2 = 2.7)

2014-01-25 Thread Kyle Guinn
On 1/25/14, Mikko Värri v...@linuxbox.fi wrote: What Willy and Matteo are describing is, in my books, an optimization of dependency tree: removal of dependencies if they form a diamond graph. Is this optimization useful? I don't see any benefit, it just loses information. My vote would be to