Date: Fri, 14 Jan 2005 17:02:50 +0300 From: Sergey Matveychuk <sem@FreeBSD.org> To: Adi Pircalabu <apircalabu@bitdefender.com> Cc: freebsd-ports@freebsd.org Subject: Re: HEADS UP: pkg-plist strict enforcement starting Message-ID: <41E7D10A.8070308@FreeBSD.org> In-Reply-To: <20050114155745.179a1bfe@apircalabu.dsd.ro> 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> <20050114155745.179a1bfe@apircalabu.dsd.ro>
next in thread | previous in thread | raw e-mail | index | archive | help
Adi Pircalabu wrote: > 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 :| > What port are you talking about? And why it's a bad thought for you to remove files if they are not changed. -- Sem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41E7D10A.8070308>