Date: Mon, 31 Oct 2011 18:52:58 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Chris Rees <utisoft@gmail.com> Cc: ports@freebsd.org Subject: Re: An intruiging INDEX problem -- slave ports + make.conf KNOBS Message-ID: <4EAEEE8A.8020601@infracaninophile.co.uk> In-Reply-To: <CADLo839VEniObE%2BPvGy-BPYwki=7G8QmZsRHt_gTcD4ESSZPyQ@mail.gmail.com> References: <CADLo839VEniObE%2BPvGy-BPYwki=7G8QmZsRHt_gTcD4ESSZPyQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7AC6AEE82C35265FCC0EEF3A Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 31/10/2011 17:39, Chris Rees wrote: > Apparently if you define something in make.conf that slave ports also > define, then a generated INDEX becomes useless... >=20 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/162088 >=20 > Basically, jpeg2ps-a4 -slave port of-> jpeg2ps-letter which defines > A4=3Dyes, and turns jpeg2ps into jpeg2ps-a4, thus duplicating INDEX > records. Unfortunately, the master port is indexed first, so > jpeg2ps-a4 is left with an incorrect origin... >=20 > Does anyone have any clever ideas around this? One or two. The generic code for building the INDEX treats this as an error, but I don't see why that should be so. Either you decide that the package name column (the 1st column) should be the unique entry in the INDEX and so you drop any duplicates, or you decide that the second column -- directory path of the port -- should be the unique field. The second option there makes more sense to me, as it better reflects reality: with certain make variable settings there will be two or more directories within the ports tree where building the port will result in installing exactly the same port. However the assumption made by most of the software that interacts with the INDEX is that the first column is the unique key. Any way, my ports-mgmt/p5-FreeBSD-Portindex code will generate an INDEX file for you despite this sort of collision. By default it operates to make the first column the unique key, but that can be very easily changed if wanted. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW --------------enig7AC6AEE82C35265FCC0EEF3A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6u7pEACgkQ8Mjk52CukIyFswCeLFv70bF7/0sosxJThAvNGfj+ v6gAn3VCFQAMjpNqDF4JZVPZz1y1vrn1 =vnCy -----END PGP SIGNATURE----- --------------enig7AC6AEE82C35265FCC0EEF3A--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EAEEE8A.8020601>