Date: Mon, 10 Jan 2011 20:30:58 +0300 From: Eygene Ryabinkin <rea@freebsd.org> To: Anton Shterenlikht <mexas@bristol.ac.uk> Cc: freebsd-ports@freebsd.org Subject: Re: incomplete pkg-plist for print/teTeX-texmf Message-ID: <2oLRXl/Jpqz4YgoVq3MShnmlbBE@fEEwdAuY7Lvf1o%2BSaK2fw%2BgdbpE> In-Reply-To: <20110110145426.GA96212@mech-cluster241.men.bris.ac.uk> References: <20110110140145.GA94753@mech-cluster241.men.bris.ac.uk> <e/6IMak3te8mOCqq%2BW8SYwNi8yo@fEEwdAuY7Lvf1o%2BSaK2fw%2BgdbpE> <20110110145426.GA96212@mech-cluster241.men.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--rz+pwK2yUstbofK6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Mon, Jan 10, 2011 at 02:54:26PM +0000, Anton Shterenlikht wrote: > But still, why doesn't pkg_info -W say so? Because it operates on the real entries of +CONTENTS, but ls-R are created via @exec and removed via @unexec. =46rom the other hand, @unexec is spawned after the ls-R =66rom teTeX-texmf will be removed, so such construction (when some file contains both in the pkg-plist and is removed via @unexec using rm -f <file>) will be harmless and will make that file to appear in 'pkg_info -W <file>'. I don't know what is the general policy for such occurences, porter's handbook has no such information and I had faced such thing for the first time. Anyone? --=20 Eygene Ryabinkin ,,,^..^,,, [ Life's unfair - but root password helps! | codelabs.ru ] [ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ] --rz+pwK2yUstbofK6 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iF4EAREIAAYFAk0rQlEACgkQFq+eroFS7PvzjwD/bUezC/icZJE/N7FpkprOmi4t MaM90vs+Dh4pFQLi8U8A/0Z6F9N+GD7m6Jg9Eze+T+JdOwT5REap96vudQQJHkYv =fvvR -----END PGP SIGNATURE----- --rz+pwK2yUstbofK6--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2oLRXl/Jpqz4YgoVq3MShnmlbBE>