I have not had enough experience with VTK to know how compatible it is
across minor version releases. To provide flexibility, I've assumed that
vtkXY should be sufficient to provide the major.minor (X.Y) version
specificity for any port that depends on VTK (ie, I've not considered vtkXYZ
On Apr 14, 2009, at 19:02, Darren Weber wrote:
On Mon, Apr 13, 2009 at 2:52 PM, Chris Scharver wrote:
On Monday, April 13, 2009, at 04:49PM, Darren Weber wrote:
This is a thread to discuss naming conventions for VTK in macports.
Macports has the following VTK ports (as of 04/13/2009):
VTK
On Apr 14, 2009, at 19:27, Darren Weber wrote:
The conclusion to be drawn from this part of our discussion is that
any ports that depend on a specific version of VTK can specify that
version dependency only if there is a version specific port
available (ie, vtkXY). It is not possible for
Ryan Schmidt wrote:
On Apr 14, 2009, at 19:02, Darren Weber wrote:
Note that Debian use the names libvtk-* to be explicit that VTK is a
library, but this is not the case in FreeBSD.
We don't seem to have a standard for prefixing library port names with
lib or not in MacPorts. Some do
On Apr 15, 2009, at 09:12, Joshua Root wrote:
Ryan Schmidt wrote:
On Apr 14, 2009, at 19:02, Darren Weber wrote:
Note that Debian use the names libvtk-* to be explicit that VTK
is a
library, but this is not the case in FreeBSD.
We don't seem to have a standard for prefixing library port
Proposed summary:
Where possible, do not use portmajorminor (eg: vtk54), rather port
should be the latest STABLE version (eg: the port named 'vtk' should contain
5.2.x at the time of this writing). Any version of a port that is near the
cutting edge must have the -devel suffix on the port name
I agree with Ryan, that separate ports provide more clarity for dependency
specifications, but I do not understand macports variants very well. For
instance, there is a track ticket on VTK with some discussion about this
issue, see:
http://trac.macports.org/ticket/19000
In that ticket, tgamblin
This is really more of a development question and not a usage
question so macports-dev may be a better place to continue this.
On Apr 14, 2009, at 12:55, Darren Weber wrote:
I agree with Ryan, that separate ports provide more clarity for
dependency specifications, but I do not understand
On Mon, Apr 13, 2009 at 2:52 PM, css...@mac.com wrote:
On Monday, April 13, 2009, at 04:49PM, Darren Weber
dwe...@macports.org wrote:
This is a thread to discuss naming conventions for VTK in macports.
Macports has the following VTK ports (as of 04/13/2009):
VTK @4.4.2 (graphics)
On Tue, Apr 14, 2009 at 2:23 PM, Ryan Schmidt ryandes...@macports.orgwrote:
This is really more of a development question and not a usage question so
macports-dev may be a better place to continue this.
On Apr 14, 2009, at 12:55, Darren Weber wrote:
I agree with Ryan, that separate ports
This is a thread to discuss naming conventions for VTK in macports.
Macports has the following VTK ports (as of 04/13/2009):
VTK @4.4.2 (graphics)
3D visualization toolkit
vtk5 @5.2.1 (graphics, devel)
3D visualization toolkit
In the Debian distribution, there are quite a few
On Monday, April 13, 2009, at 04:49PM, Darren Weber dwe...@macports.org
wrote:
This is a thread to discuss naming conventions for VTK in macports.
Macports has the following VTK ports (as of 04/13/2009):
VTK @4.4.2 (graphics)
3D visualization toolkit
vtk5 @5.2.1 (graphics, devel)
3D
On Apr 13, 2009, at 16:52, css...@mac.com wrote:
On Monday, April 13, 2009, at 04:49PM, Darren Weber wrote:
This is a thread to discuss naming conventions for VTK in macports.
Macports has the following VTK ports (as of 04/13/2009):
VTK @4.4.2 (graphics)
3D visualization toolkit
vtk5
13 matches
Mail list logo
