[MacPorts] #29145: llvm: don't use a versioned docdir
MacPorts
noreply at macports.org
Sat Apr 16 16:22:58 PDT 2011
#29145: llvm: don't use a versioned docdir
-------------------------------------+--------------------------------------
Reporter: ryandesign@… | Owner: mfeiri@…
Type: enhancement | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Keywords: haspatch | Port: llvm
-------------------------------------+--------------------------------------
Changes (by mfeiri@…):
* owner: erickt@… => mfeiri@…
* cc: mfeiri@… (removed)
* cc: erickt@… (added)
* status: new => assigned
Comment:
I think this patchfile is included for historic reasons only and under
normal circumstances I'd support every effort to reduce deviations from
upstream. But in this case I think we need to think about _fully_
versioned ports of llvm. The llvm-gcc42 compiler just reached its end-of-
life and will continue to depend on llvm version 2.9 while our llvm port
will move on to newer versions. I currently see three options:
a) llvm29, llvm30, llvm31, .... where each port conflicts the other ports.
This will frequently require manual conflict resolution during upgrades of
dependent ports (e.g. clang).
b) llvm29, llvm30, llvm31, .... where each port installs headers in
versioned subdirectories and renames executables with versioned suffixes.
Notify users about this and patch dependent ports to use these specific
directories/executables. Maybe introduce something like a llvm_select
tool.
c) Continue the llvm port as is but do not support llvm as a build
dependency. Notify users about this and change all dependent ports to
build their own compatible version of llvm and link statically
None of these options seems particularly attractive. Suggestions?
--
Ticket URL: <https://trac.macports.org/ticket/29145#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list