[Slackbuilds-users] Very simple way of finding dependency

Jeremy Hansen jebrhansen+SBo at gmail.com
Wed Sep 13 13:31:25 UTC 2017

On Wed, Sep 13, 2017, 8:53 AM Gerardo Zamudio <gerardo.zamudio at linux.com>

> On 09/13/2017 07:35 AM, Willy Sudiarto Raharjo wrote:
> >
> > Please note that we don't provides binary packages like ARCH Linux. We
> > only provide scripts to build a source into a package.
> What's wrong with a file that lists the binaries the script will generate?
> > Another thing to consider is that the resulting files may be different
> > from one to another due to optional dependencies installed on each
> > machines. It would be a nightmare for maintainer to track all files for
> > each combination of optional dependencies
> >
> Why should the file include *optional* dependencies and build
> parameters? The SBo scripts are supposed to be tested in a clean, full
> install of Slackware.

Why should SBo, which doesn't provide binary packages, provide a listing of
what is in a binary package?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170913/80f05719/attachment.html>

More information about the SlackBuilds-users mailing list