On 2013-11-26 19:20 , Ryan Schmidt wrote: > > On Nov 26, 2013, at 00:06, Mark Evenson wrote: > >> Other than I don’t know any other example of a port name with a period (“.”) >> in it, so we might want to check that including version in this way doesn’t >> break anything, this looks like a perfectly acceptable proposal to me. > > perl5.12, p5.12-*, clang-3.3, llvm-3.3, etc. > > We also have ports that run the numbers together, like python33 or php55, but > this has a built-in assumption that version number components don’t grow to > more than 1 digit, which isn’t always the case (e.g. perl5.12); being > sufficiently future-proof isn’t a bad idea. > > The “-“ in e.g. clang-3.3 worried me because I thought MacPorts would confuse > it with the syntax for disabling a variant, but it doesn’t seem to have been > a problem.
To quote 'port lint': "Names should only contain alphanumeric characters, underscores, dashes or dots." - Josh _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
