[102939] trunk/dports/graphics

Ryan Schmidt ryandesign at macports.org
Wed Feb 13 13:13:36 PST 2013

On Feb 13, 2013, at 07:36, Michael Dickens wrote:
> On Feb 12, 2013, at 11:34 PM, Ryan Schmidt wrote:
>> When there are multiple versions of a port, we have two possible naming conventions.
>> One is to have two ports: foo and foo-devel, with foo being stable and foo-devel being development or experimental. foo and foo-devel conflict with one another. Ports that declare dependencies on these ports do so in a way that either could satisfy it. (c.f. graphviz{,-devel}, pango{,-devel}, glib2{,-devel}, cairo{,-devel}, libpixman{,-devel}).
>> The other is to have two or more ports fooXY, where XY is a part of the version number. The latest of these might not be stable yet, but will be in the fullness of time (c.f. php55, llvm-3.3, clang-3.3). The ports do not conflict with one another. Ports may declare dependencies on whichever version is required. Different ports can declare dependencies on different fooXY versions and they can all be installed simultaneously.
>> So, in the qwt ports, you are mixing and matching these two styles.
> True.  And, I take it that the "MacPorts powers that be" would prefer if
> ports used one style or the other, but not mixing an matching, yes? 

If you can, that would be great. The naming convention gives the user certain expectations about how the port behaves, which is currently not happening for the qwt ports.

> That's OK; I think it's pretty easy to change the install location of
> these ports, and also to specify which to use in any dependent port
> (and, I believe, there are not very many dependent ports).  Should take
> a few days for me to deal with this and test it well enough. - MLD

More information about the macports-dev mailing list