ports need a uniq identifier, do you have any suggestion?

[Baptiste Daroussin]

Hi all,

In the ports tree we lack a unique identifier, while we could live without it
until now, it is more than needed for 2 upcoming features: pkgng and stage
directory support.

unique means something that will always be the same what ever the options are
and what ever the runtime they use are. But also means unique in term of in the
whole ports no other package will share its identifier.

currently the only equivalent of this in the ports tree is the origin of a
package, which will no more be unique with the upcoming sub package support
(coming along with stage directory) aka 1 origin to produce n package.

UNIQUENAME and LATEST_LINK fails in that area because they both can change
according to the runtime: py27- for example which will become py30- if you
change the default python.
LATEST_LINK by default also append the PKGNAMEPREFIX which some ports can be
really creative with.

should we introduce something new, should we fix one of the above? do you have
any suggestion?

regards,
Bapt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20120611/e9202130/attachment.pgp