Date: Fri, 14 Jan 2005 15:57:45 +0200 From: Adi Pircalabu <apircalabu@bitdefender.com> To: freebsd-ports@freebsd.org Subject: Re: HEADS UP: pkg-plist strict enforcement starting Message-ID: <20050114155745.179a1bfe@apircalabu.dsd.ro> In-Reply-To: <20050114133050.GN69532@voodoo.oberon.net> References: <20050113062739.GA28658@xor.obsecurity.org> <Pine.LNX.4.44.0501131148520.25402-100000@pancho> <20050113180504.GA26064@xor.obsecurity.org> <20050114130404.250d6e26@apircalabu.dsd.ro> <20050114112918.GF69532@voodoo.oberon.net> <1105704398.41e7b5ce7dc5e@buexe.b-5.de> <20050114144353.1aad2014@apircalabu.dsd.ro> <20050114133050.GN69532@voodoo.oberon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 14 Jan 2005 14:30:50 +0100
Kirill Ponomarew <krion@voodoo.oberon.net> wrote:
> > In my case, after port's deinstall, there will always be files left
> > in${PREFIX}/portname/. Is this a reason for tagging the port
> > BROKEN/IGNORE?
>
> Leftovers are considered to be a reason for BROKEN tag.
I understand your point, it is very decent from an application to
clean-up after deinstall. But sometimes it is not appropriate to
complete delete all the dirs/files, especially when the files are, let's
say, system-wide configuration files. What if I upgrade the software? Do
I have to backup the configuration before upgrading, and then restore it
after the upgrade completed? I'm too lazy for that, I'd like a smooth
and easy upgrade :)
In my case, it is very common for the port to change/modify/delete files
at runtime, even configuration files are changed while the product is
running. If this is the reason for marking the port BROKEN I'm in big
trouble :|
--
Adrian Pircalabu
Public KeyID = 0xF902393A
--
This message was scanned for spam and viruses by BitDefender.
For more information please visit http://www.bitdefender.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050114155745.179a1bfe>