Date: Sun, 29 Jan 2006 12:43:33 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Andrew Pantyukhin <infofarmer@gmail.com> Cc: cvs-ports@freebsd.org, Kris Kennaway <kris@obsecurity.org>, pav@freebsd.org, cvs-all@freebsd.org, ports-committers@freebsd.org Subject: Re: cvs commit: ports/www/yabb Makefile pkg-plist ports/www/yabb/files pkg-message.in Message-ID: <20060129014333.GI2341@turion.vk2pj.dyndns.org> In-Reply-To: <cb5206420601281247g237c9013h7bcd2e96d93f75c0@mail.gmail.com> References: <200601281659.k0SGxWdP049268@repoman.freebsd.org> <20060128193852.GA30951@xor.obsecurity.org> <cb5206420601281144g18d49bf2lf2e22081adbf0c3b@mail.gmail.com> <20060128195138.GA31594@xor.obsecurity.org> <cb5206420601281213i6decb15cpc594b136d06540b8@mail.gmail.com> <1138480529.36184.57.camel@localhost> <cb5206420601281247g237c9013h7bcd2e96d93f75c0@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2006-Jan-28 23:47:42 +0300, Andrew Pantyukhin wrote: >On 1/28/06, Pav Lucistnik <pav@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060129014333.GI2341>