HEADS UP: pkg-plist strict enforcement starting

Kris Kennaway kris at obsecurity.org
Fri Jan 14 06:27:58 PST 2005

On Fri, Jan 14, 2005 at 04:24:05PM +0200, Adi Pircalabu wrote:
> On Fri, 14 Jan 2005 17:02:50 +0300
> Sergey Matveychuk <sem at 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.

The main case you need to worry about is when someone (e.g. package
cluster) does 'make install deinstall'.  It's OK, but not ideal, for
the package to leave behind some runtime-created files when the
software has been used or configured by the user.  You should then add
a pkg-deinstall message warning about where the leftover files live,
if they exist, so the administrator can choose to delete them by hand.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20050114/ff3cff11/attachment.bin

More information about the freebsd-ports mailing list