Date: Fri, 14 Jan 2005 16:24:05 +0200 From: Adi Pircalabu <apircalabu@bitdefender.com> To: freebsd-ports@freebsd.org Subject: Re: HEADS UP: pkg-plist strict enforcement starting Message-ID: <20050114162405.2777fa0a@apircalabu.dsd.ro> In-Reply-To: <41E7D10A.8070308@FreeBSD.org> 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> <41E7D10A.8070308@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 14 Jan 2005 17:02:50 +0300 Sergey Matveychuk <sem@FreeBSD.org> wrote: > What port are you talking about? It's BitDefender Antivirus I have to port on FreeBSD. The architecture and behaviour is similar to Linux version. Besides creating the configuration files at install time from generic .dist files, it also creates new files (especially AV definition and signature files), along with modifying existing ones. A typical situation: A new AV engine is created and the decision is to put the detection code in a new file, which was not present in the system after install. Obviously the file was not registered at install so I can not delete it when deinstalling (I have no idea of the filename, size, md5). Therefore the file will be left as is after install, leading to a broken port. > And why it's a bad thought for you to remove files if they are not > changed. I did not mean that, it's common sense to delete them if they have not changed. -- 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?20050114162405.2777fa0a>