Fwd: Naming Scheme for MacPorts Octave versions

Michael Dickens michaelld at macports.org
Mon Dec 12 18:17:40 PST 2011

Forwarded with permission from Lukas.  I just use Octave (-devel)
in a basic sense, so I'll trust what he says -- and, it makes
sense too if folks are using octave (3.2) as well as *-devel
(3.4).  But, as I'm trying to back off of doing this sort of work
I'll defer to others to make any decision. - MLD
Begin forwarded message:

From: Lukas Reichlin <lukas.reichlin at gmail.com>
Date: December 11, 2011 3:47:03 PM EST
To: Michael Dickens <michaelld at macports.org>
Subject: Naming Scheme for MacPorts Octave versions
Hi Michael
For reasons I don't understand, MacPorts "octave" port is still
version 3.2.4. The current release, version 3.4.3, is only
available as "octave-devel". Since Octave 3.6.0 will be available
soon and we don't want an "octave-devel-devel", something needs
to be done. Probably there are people who still want the outdated
Octave 3.2, so I propose to change the port names as following:
octave32  (former octave)
octave34  (former octave-devel)
octave36  (when it is available)
This naming scheme is usual for python, gcc and since today with
clang and llvm.
Additionaly, this name scheme should be applied to the extra
packages as well, because they rely on certain octave versions:
octave-control (1.0.11) becomes octave32-control, and a new
octave34-control (2.2.3) could be added. This is similar to
python, where we have py26-xyz, py27-xyz and so on.
What do you think?
Best regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20111212/2f70761a/attachment.html>

More information about the macports-dev mailing list