cvs commit: ports/www/yabb Makefile pkg-plist ports/www/yabb/files pkg-message.in

[Andrew Pantyukhin]

On 1/28/06, Pav Lucistnik <pav at freebsd.org> wrote:
> Andrew Pantyukhin píše v so 28. 01. 2006 v 23:13 +0300:
> > On 1/28/06, Kris Kennaway <kris at obsecurity.org> wrote:
> > > On Sat, Jan 28, 2006 at 10:44:29PM +0300, Andrew Pantyukhin wrote:
> > > > On 1/28/06, Kris Kennaway <kris at obsecurity.org> wrote:
> > > > > On Sat, Jan 28, 2006 at 04:59:32PM +0000, Pav Lucistnik wrote:
> > > > > > pav         2006-01-28 16:59:32 UTC
> > > > > >
> > > > > >   FreeBSD ports repository
> > > > > >
> > > > > >   Modified files:
> > > > > >     www/yabb             Makefile pkg-plist
> > > > > >     www/yabb/files       pkg-message.in
> > > > > >   Log:
> > > > > >   - Now installs into /usr/local/www instead of /usr/local/www/{data,cgi-bin}
> > > > > >   - Data flatfiles are now cautiously left behind whether they have changed or not
> > > > >
> > > > > It's not OK for packages to leave files behind after deinstallation.
> > > > > Can you please fix this?
> > > > >
> > > > > Kris
> > > > >
> > > > >
> > > > >
> > > >
> > > > NO_PACKAGE was set in the same commit, if that helps
> > >
> > > It's still not OK, but now you just hid the problem from the package
> > > cluster :)
> > >
> > > Kris
> > >
> > >
> > >
> >
> > No, it's not about the package cluster. The plist is incomplete,
> > that's the simplest/stupidest way to deal with 3 dozen important
> > data files in different dirs.
> >
> > I wish there was some way to leverage the file checksums in
> > the package database and tell pkg_delete (and pkg_deinstall,
> > too) not to remove any modified files unless the user has very
> > specifically told otherwise. AFAIK there isn't. I guess I'll have
> > to do it manually (in pkg-<scripts>). I haven't done it yet, but
> > I felt it was not _that_ important. Warnings are in place,
> > package building is denied.
>
> There is a documented way for dealing with such files:
>
> http://www.freebsd.org/doc/en/books/porters-handbook/plist-config.html

Yes, and it sucks. It works when it's about a couple of
configuration files. But it can't be used as a general
purpose way of handling modified files. We'll end up
installing double trees for all such ports and comparing
them before deinstallation.

Checksums are good for that, our pkg system can create
them, can tell us if a file has been modified, hell it can
even deinstall a package keeping all modified files
intact. But it's not flexible enough yet, so when I use
portupgrade all files are going to get deleted anyway.