Re: [Slackbuilds-users] Optional dependencies in info file

On 29/11/15 17:56, Willy Sudiarto Raharjo wrote: What do you think about putting optional (available from SBo) dependencies in the info file? I think that would allow for further automation. What I have noticed is that, it's sometimes hard to go through the README and spot all the optional

Re: [Slackbuilds-users] Optional dependencies in info file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This would require that package managers be added the feature that enables them to look at the optional line as well. They would need to have the ability to ask if the optional dependencies are added and which specific deps depending on which

Re: [Slackbuilds-users] Optional dependencies in info file

On 29/11/15 18:51, Brenton Earl wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This would require that package managers be added the feature that enables them to look at the optional line as well. They would need to have the ability to ask if the optional dependencies are added and

Re: [Slackbuilds-users] Optional dependencies in info file

2015-11-29 18:10 GMT+01:00 Andrzej Telszewski : > On 29/11/15 17:56, Willy Sudiarto Raharjo wrote: >>> >>> What do you think about putting optional (available from SBo) >>> dependencies in the info file? >>> I think that would allow for further automation. >>> >>> What I

Re: [Slackbuilds-users] Optional dependencies in info file

On 29/11/15 18:17, Matteo Bernardini wrote: 2015-11-29 18:10 GMT+01:00 Andrzej Telszewski : On 29/11/15 17:56, Willy Sudiarto Raharjo wrote: What do you think about putting optional (available from SBo) dependencies in the info file? I think that would allow for further

Re: [Slackbuilds-users] Optional dependencies in info file

> What do you think about putting optional (available from SBo) > dependencies in the info file? > I think that would allow for further automation. > > What I have noticed is that, it's sometimes hard to go through the > README and spot all the optional deps, because everybody writes README > as

Re: [Slackbuilds-users] Optional dependencies in info file

One of the nice things about the .info files is that just about anything can be added to them; automated build tools will generally ignore any new fields you may choose to add. From my clone of the SBo repo, I have a branch named "spbuilder" (after the name of the build tool I use). In that

Re: [Slackbuilds-users] Optional dependencies in info file

On 29/11/15 23:56, Christoph Willing wrote: The only work is adding the options you want but that is also the advantage - you have the options _you_ want rather some some arbitrary set of options the maintainer wants or believes end users will want. Actually, it's like that at the moment and

Re: [Slackbuilds-users] Optional dependencies in info file

> do you suggest that all dependencies are listed in the REQUIRES field or > that there is a new field eg OPTIONAL introduced? > > for example in case of EMBOSS: > > REQUIRES="jdk" > > OPTIONAL="clustalw primer3" That will make maintainer and admin's job becomes more complicated :) -- Willy

Re: [Slackbuilds-users] Optional dependencies in info file

On 29/11/15 18:41, Petar Petrov wrote: do you suggest that all dependencies are listed in the REQUIRES field or that there is a new field eg OPTIONAL introduced? for example in case of EMBOSS: REQUIRES="jdk" OPTIONAL="clustalw primer3" 2015-11-29 19:10 GMT+02:00 Andrzej Telszewski

[Slackbuilds-users] Optional dependencies in info file

Hi, What do you think about putting optional (available from SBo) dependencies in the info file? I think that would allow for further automation. What I have noticed is that, it's sometimes hard to go through the README and spot all the optional deps, because everybody writes README as

[Slackbuilds-users] Grass plugin in Qgis

Hi, thanks for SBo slackbuilds, Qgis-2.10 need Grass6 but SBo have only Grass7. I use Qgis SBo slackbuild to install Qgis-2.12.1 that needs qca-2.0.3+, Slack 14.1 have qca-2.0.2 I upgrade qca with slackbuild for current (2.0.3 + patch) It works fine and I have now Grass plugin installed:

Re: [Slackbuilds-users] Grass plugin in Qgis

> Hi, > thanks for SBo slackbuilds, > Qgis-2.10 need Grass6 but SBo have only Grass7. > I use Qgis SBo slackbuild to install Qgis-2.12.1 > that needs qca-2.0.3+, Slack 14.1 have qca-2.0.2 > I upgrade qca with slackbuild for current (2.0.3 + patch) Hi Thanks for the info about Qgis, but we

[Slackbuilds-users] Nodejs vs node

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I notice there are two similar packages on SBo: nodejs and node. What's the difference between them besides the version number and npm completion scripts? - -- Gerardo Zamudio Linux System Administrator https://gerardozamudio.mx -BEGIN PGP

Re: [Slackbuilds-users] Nodejs vs node

> > Thanks for the explanation, Ryan. It makes sense and I agree we should > keep both. It might be a good idea to give this a brief mention in the > README, something like "nodejs is the project that was forked from > node and merged back. It includes many breaking changes". Maybe advise > users

Re: [Slackbuilds-users] Nodejs vs node

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/29/2015 07:47 PM, Ryan P.C. McQuen wrote: > Below is the explanation I sent to the SBo admin list upon > submitting 'nodejs': > > I will do my best to explain the mess created here by upstream. > > node was first. Unfortunately it was

Re: [Slackbuilds-users] Optional dependencies in info file

On 11/30/2015 09:11 AM, Andrzej Telszewski wrote: On 29/11/15 23:56, Christoph Willing wrote: The only work is adding the options you want but that is also the advantage - you have the options _you_ want rather some some arbitrary set of options the maintainer wants or believes end users will

Re: [Slackbuilds-users] Optional dependencies in info file

do you suggest that all dependencies are listed in the REQUIRES field or that there is a new field eg OPTIONAL introduced? for example in case of EMBOSS: REQUIRES="jdk" OPTIONAL="clustalw primer3" 2015-11-29 19:10 GMT+02:00 Andrzej Telszewski : > On 29/11/15 17:56,