[Slackbuilds-users] Checking Dependencies

[Lehman Black]

The Slackware package manager doesn't have any dependency checking built in.
The usual way a user discovers a program's dependencies is by visiting that
program's web site. Or if they are compiling a package, the build process
will usually fail in the configure stage with something like "can't find
package X"

If you want dependency checking there are a couple of projects that add it
to the Slackware package manager. you might have a look at swaret or
slapt-get. freshmeat.net also has some different package managers for
Slackware.

On 2/23/07, Rich Shepard <rshepard at appl-ecosys.com> wrote:
>
> On Fri, 23 Feb 2007, Lehman Black wrote:
>
> > Usually SlackBuilds on slackbuilds.org do not check dependancies. A list
> > of dependancies should be placed in the
> > README<http://slackbuilds.org/guidelines/>file to let the person
> > downloading the script what other SlackBuilds/Packages they would need
> to
> > install before running the script.
>
> Lehman,
>
>    Stepping back to look at this from the user's perspective, I can see
> your
> point. Preparing the package is one thing, installing and using the
> application is another.
>
>    But, would the user necessarily know the requirements before installing
> the package? Only if the source mentioned them. I guess there's no
> dependency checking that can be added to the package that would activate
> during an install or upgrade.
>
> Rich
>
> --
> Richard B. Shepard, Ph.D.               |    The Environmental Permitting
> Applied Ecosystem Services, Inc.        |          Accelerator(TM)
> <http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax:
> 503-667-8863
> _______________________________________________
> Slackbuilds-users mailing list
> Slackbuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20070223/5c0e1f15/attachment-0002.html