Date: Mon, 11 Jun 2012 12:34:16 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Baptiste Daroussin <bapt@freebsd.org> Cc: ports@freebsd.org Subject: Re: ports need a uniq identifier, do you have any suggestion? Message-ID: <4FD5D7B8.9080504@infracaninophile.co.uk> In-Reply-To: <20120611103221.GU60433@ithaqua.etoilebsd.net> References: <20120611043001.GO60433@ithaqua.etoilebsd.net> <4FD591DF.3060808@infracaninophile.co.uk> <20120611103221.GU60433@ithaqua.etoilebsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig7DAD64CC3C9D3B7795A1D430
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 11/06/2012 11:32, Baptiste Daroussin wrote:
>> UNIQUENAME importance being because the default location for a port's
>> > OPTIONSFILE is derived from it, and non-uniqueness can lead to ports=
>> > fighting over control of that file? Which is bad when unintentional=
,
>> > but can be useful for some related ports to share the same options s=
ettings.
> Well this is the right thing to do but looking at bsd.port.mk and the c=
hanges
> needed I get bored and gave up :(
I haven't looked at what would be necessary to fix UNIQUENAME collisions
in any great detail, but I think a number are due to setting PORTNAME to
something basically incorrect.
>> > Does pkgng really need LATEST_LINK at all? As far as I recall, that=
>> > only exists so that the user can say:
> Well no pkgng doesn't need it at all except for pkg itself for the boot=
strap :)
Hmmm... so there just has to be pkg.txz at some predictable URL(s) on
the FBSD mirrors? That doesn't sound like enough to justify keeping
LATEST_LINK related bits in the ports tree.
>> > I don't see the problem with port prefixes changing UNIQUENAME. Isn=
't
>> > py27-foo conceptually a different port to py30-foo ? Yes, they are
>> > built from the same port ORIGIN, but you already intend dropping the=
>> > one-to-one correspondence between port ORIGINS and packages with the=
>> > introduction of sub-ports.
> Maybe they are different packages, but they have the same options, and =
from
> pkgng we should be able to detect it as the same package just a differe=
nt
> runtime which is what they are.
I think I see. You're thinking of packages that install the same files,
but maybe in a different location (eg. SITE_PERL) or that register
run-time dependencies on a number of different possible providers.
Couldn't that boil down to having several alternate .MANIFEST files in
the pkg? Plus some sort of final-location-independent way of naming the
files to be installed by the package?
On the matter of having alternate RUN_DEPENDS to be set at install time?
I've wanted to do something like that with databases/phpmyadmin for
ages. Most of the optional dependencies there are autodetected by the
PHP code at run-time, so it should be possible to just ask the user
which of them they want to have during pkg installation.
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
--------------enig7DAD64CC3C9D3B7795A1D430
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/
iEYEARECAAYFAk/V18QACgkQ8Mjk52CukIxHBACfZ39I2HAY+dmx56DvTUojCuLy
OkAAoIJ3GJWj2y8CcyoufwgOYeU0oBWx
=f1wY
-----END PGP SIGNATURE-----
--------------enig7DAD64CC3C9D3B7795A1D430--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FD5D7B8.9080504>