Date: 03 May 2000 03:24:48 -0700 From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) To: Gary Jennejohn <garyj@muc.de> Cc: ports@freebsd.org Subject: Re: lists of files and directories missing from PLIST Message-ID: <vqcu2gg7wy7.fsf@silvia.hip.berkeley.edu> In-Reply-To: Gary Jennejohn's message of "Tue, 02 May 2000 22:09:27 %2B0200" References: <200005022009.WAA08799@peedub.muc.de>
next in thread | previous in thread | raw e-mail | index | archive | help
* From: Gary Jennejohn <garyj@peedub.muc.de>
* Yes, but you say that leaving a file/directory behind will become a fatal
* error at some time in the future. If I leave some files in a dir because
* I know another port needs them, then that should not be considered fatal.
Um, you are not allowed to do that. What if those two ports are
installed from packages? Assuming you are just listing them in PLIST
and not doing an "@exec echo foo bar > file" type of tricks, the first
pkg_delete will remove the file, leaving remaining packages crippled.
The requirement would be that "starting from an empty /var/db/pkg and
${PREFIX}, install a port and all its dependent packages, then
pkg_delete everything listed in /var/db/pkg, ${PREFIX} should not
contain anything that is not listed in ${MTREE_FILE}".
If you are taking some care to create a file that can be shared
between multiple ports, make the last port that's pkg_deleted remove
the file. This will pass the above test and is exactly what my
proposed info/dir patch will do.
Satoshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?vqcu2gg7wy7.fsf>