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

Peter Jeremy peterjeremy at optushome.com.au
Sat Jan 28 17:43:44 PST 2006


On Sat, 2006-Jan-28 23:47:42 +0300, Andrew Pantyukhin wrote:
>On 1/28/06, Pav Lucistnik <pav at freebsd.org> wrote:
>> 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.

It's the best we've got at present.  There are also some advantages to
having a "sample" configuration file present to assist the user.  If
you're only talking about a few files, the current approach is
reasonable.  If you're talking about lots of files and/or large files
then you do need something better.

>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.

It wouldn't be too difficult to make pkg_install refuse to over-write
files but that is likely to cause as many problems as it solves.
Ideally pkg_install would warn that a file already existed and rename
it rather than over-writing it - whilst package infrastructure can't
do this, you could do it yourself in a pre-install script.

-- 
Peter Jeremy


More information about the cvs-ports mailing list