On Sun, 27 Feb 2000, Frederick Bruckman wrote:
> Yeah, it's not especially useful like it is. I have some idea to use
> RUN_DEPENDS differently, but I don't have time to develop it right now.

I assume you'll let tech-pkg know when the time is ripe. 

What do we do with the unused code until then? (Affected are at least the
references to RUN_DEPENDS and run-depends, and - see my other mail -
build-depends, BUILD_DEPENDS and esp. the DEPENDS_USE macro).


> OK, not the update target as such, but the deinstall target (1.408).
> It's not clear to me why it's necessary, only now, to delete the
> BUILD_DEPENDS. Even if you have a package that requires a particular
> version of, say, automake to build, you still lose when the user runs
> "pkg_delete" manually.

OK, IC... i'm not familiar with the update code - can you see if the
following makes things better (in the root-deinstall target):

-.if (${DEINSTALLDEPENDS} != "NO")
+.if (${DEINSTALLDEPENDS} == "YES")

(Although that's probably broken from the naming but hey, I was not the
one who overloaded the simple yes/no interface :-)


 - Hubert

-- 
NetBSD - Better for your uptime than Viagra