kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Warn about too-generous wildcard dependencies, which may prove bogus (using

Browse source 
tk-* as example). Also fix no more accurate info regarding wildcard deps -
they are now retained even for binary packages.

Suggested by David Brownlee.
This commit is contained in:
jdolecek 2000-04-20 16:06:23 +00:00
parent 11d1f7b147
commit c650583872
1 changed files with 14 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
Packages.txt
View file

@ -1,4 +1,4 @@
# $NetBSD: Packages.txt,v 1.83 2000/03/10 17:57:11 hubertf Exp $
# $NetBSD: Packages.txt,v 1.84 2000/04/20 16:06:23 jdolecek Exp $
###########################################################################
==========================
@ -1391,9 +1391,17 @@ You can also use wildcards in package dependences:
DEPENDS+= xpm-*:../../graphics/xpm
Note that these wildcards will be expanded while creating binary packages.
Thus binary package will depend on exactly the version which was installed
when they were created.
Note that such wildcard dependencies are retained when creating
binary package. The dependency is checked when installing the binary
package and any package which matches the pattern would be used.
Beware that wildard dependencies should be used with a bit of care.
Simple example for package which needs some version of Tk installed,
but doesn't care which exactly - dependency
DEPENDS+= tk-*:../../x11/tk80
would also match e.g. tk-postgresql-6.5.3, which is not what was
needed. ALWAYS ensure that the wildcard doesn't match more than it should.
(d) If your package needs some executable to be able to run correctly, this
is specified using the DEPENDS definition. The print/lyx package needs to
@ -1402,6 +1410,8 @@ and that is specified:
DEPENDS+= teTex-*:../../print/teTeX
The comment about wildcard dependencies from previous paragraph
applies here, too.
9.13 Conflicts with other packages