Date: Fri, 04 Feb 2005 19:41:29 +0100 From: Florent Thoumie <flz@xbsd.org> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: hq@freebsd.org Subject: Re: bin/77082: src/usr.sbin/pkg_install - Add 3 new macros to clean pkg-plist Message-ID: <4203C1D9.5090108@xbsd.org> In-Reply-To: <20050204183546.GA5389@odin.ac.hmc.edu> References: <200502032350.j13NoKLF045837@freefall.freebsd.org> <42039BAA.2070900@xbsd.org> <20050204183546.GA5389@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Brooks Davis wrote:
> It seems like dirrmtry should take an optional message to emit if the
> event that the directory can not be delete. That way the user can be
> informed that the directory should be removed if they are really done
> using the port.
I asked myself if I should put this feature in my patch and
I finally haven't because it required some extra-stuff
(handling optional arguments for @ commands is painful), and a
simple '@unexec [ -d ${PREFIX}/etc ] && echo ...' is easier I
guess. But that's no problem for me to include that if everybody
thinks it worth it.
> Have you thought about how to solve the boot strapping problems with
> pkg_install/pkg_delete?
I have absolutely no idea what you're talking about, I started
looking at pkg_install source yesterday at night. Could you
give me some pointers about that ?
> Our nominal pkg_install maintainer is MIA at the moment.
Ok, actually I knew eik has been working on it, but I didn't
know who was the active maintainer now.
I have thought of a new purge command, that would act like
dpkg --purge on Debian but AFAIK that would be impossible
since it would need persistent package records (that still
exists after a package has been removed as long as we have
some configuration files for this port in the tree).
--
Florent Thoumie
flz@xbsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4203C1D9.5090108>