Date: Sun, 27 Jan 2008 22:26:00 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Mikhail Teterin <mi+kde@aldan.algebra.com> Cc: Jeremy Messenger <mezz7@cox.net>, cvs-all@freebsd.org, ports-committers@freebsd.org, Edwin Groothuis <edwin@mavetju.org>, Joe Marcus Clarke <marcus@freebsd.org>, cvs-ports@freebsd.org Subject: Re: cvs commit: ports/net/ekiga pkg-plist Message-ID: <479D7578.1070504@FreeBSD.org> In-Reply-To: <200801261328.47675@aldan> References: <200801201628.m0KGSlq6037319@repoman.freebsd.org> <479B6A3D.10108@FreeBSD.org> <op.t5jru6xx9aq2h7@mezz.mezzweb.com> <200801261328.47675@aldan>
next in thread | previous in thread | raw e-mail | index | archive | help
Mikhail Teterin wrote:
> On субота 26 с╕чень 2008, Jeremy Messenger wrote:
> = Well, it's not only for package. What about users' systems that use ports?
> = What if one of user decide to uninstall ekiga? It will ending up with
> = leftover files in their system. Bump is need to have their system clean.
> = As for not like to build again, perhaps we need to come up with new
> = *VERSION like PLISTVERSION that will only fix plist without have to
> = rebuild.
>
> We don't need to come with anything for this case -- the timestamp on
> pkg-plist can (almost) always be compared with that
> of /var/db/pkg/FOO/+CONTENTS
I beg to differ, I think it can basically never be relied on. The
+CONTENTS file is updated many times after the port is installed,
either by tools like portmaster, or by the ports infrastructure
itself. (Think dependency tracking via pkgdep.)
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?479D7578.1070504>