Subject: Re: removing RUN_DEPENDS
To: Frederick Bruckman <fb@enteract.com>
From: Hubert Feyrer <feyrer@rfhs8012.fh-regensburg.de>
List: tech-pkg
Date: 02/28/2000 13:18:51
On Mon, 28 Feb 2000, Frederick Bruckman wrote:
> Now that I think about it, there really isn't anything useful there. I
> would want RUN_DEPENDS to hinge on a package, and not a binary. I
> hadn't really thought about it for the BUILD_DEPENDS, but it makes
> sense now that we can use wildcards and dewey depends.
OK, I understand this as "not needed by you".
> > -.if (${DEINSTALLDEPENDS} != "NO")
> > +.if (${DEINSTALLDEPENDS} == "YES")
>
> Hmmm. This would make "ALL", which is set unconditionally by the
> update target, lie somewhere between NO and YES:
>
> DEINSTALLDEPENDS=NO "pkg_delete"
> DEINSTALLDEPENDS=ALL "pkg_delete -r"
> DEINSTALLDEPENDS=YES "pkg_delete -r -R" + pkg_delete BUILD_DEPENDS
Someone[tm] should probably s/ALL/SOME/ there. :-)
If the fix works for you, please commit it, I cannot test it.
- Hubert
--
NetBSD - Better for your uptime than Viagra