[MacPorts] #29145: llvm: don't use a versioned docdir

MacPorts noreply at macports.org
Sat Apr 16 16:59:01 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               
-------------------------------------+--------------------------------------

Comment(by ryandesign@…):

 In this case, I'm not advocating reducing deviations from upstream (though
 generally that's a great idea); I'm advocating conformance with MacPorts
 best practices. Several years ago, Anthony Ramine (nox) decided we should
 use ${name}-${version} as our docdir name, and we tried that for awhile
 (for example, during the time that #15724 was filed and resolved), but we
 later decided there was no purpose for including the version in the docdir
 if there's only a single port, and thus only a single version active at
 any given time. That's what my patch in this ticket addresses. But if
 you're considering having multiple llvm version ports, then that might
 change things.

 Of the above options you've presented, a) is not ok; the llvm29 llvm30
 llvm31 port naming scheme implies in MacPorts that all of these can be
 installed simultaneously and they do not conflict. c) Seems needlessly
 complex. I'd say that leaves b) as the correct solution. Note that any
 hypothetical llvm_select tool would be for the user's convenience, but
 could not be used or relied upon by portfiles that need llvm.

 We can also simply b) a bit, and just create an llvm29 port for the
 benefit of the llvm-gcc42 port, and keep the llvm port continuing on to
 whatever the current version of llvm is. That would probably be the best
 plan. This matches how we've handled automake (automake17), autoconf
 (autoconf213 autoconf263), apr-util (apr-util0), etc.

-- 
Ticket URL: <https://trac.macports.org/ticket/29145#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list