[MacPorts] #33259: cmake portgroup: out of source build option, possibly by default
MacPorts
noreply at macports.org
Wed Mar 18 12:57:36 PDT 2015
#33259: cmake portgroup: out of source build option, possibly by default
---------------------------+--------------------------------
Reporter: ryandesign@… | Owner: macports-tickets@…
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: |
---------------------------+--------------------------------
Comment (by mojca@…):
Replying to [comment:44 larryv@…]:
>
> Or we could actually make use of the portgroup version number. With a
`cmake-1.1` portgroup that enables out-of-source builds by default, we’d
still have to migrate ports one at a time, but we’d need just one pass to
update the `PortGroup` command and remove obsolete workarounds. I have
this set up locally, and it seems to work fine. I’d like to commit it this
week if no one has any objections to this migration strategy.
I'm not really a fan of increasing the portgroup version number. We would
have to increase the number if we introduced some incompatible change.
Otherwise we just end up with two files (both of which need to be
maintained) with hardly any functional difference.
If most developers have a preference to keep the old functionality by
default, let's just use "`cmake.out_of_source no`" for now and start
changing the ports one-by-one. Once all the ports have been adapted and
tested, just switch the default and remove "`cmake.out_of_source yes`"
from all the ports. The last step sounds straightforward and can be fully
automated.
I really don't think that advantages of increasing the PortGroup number
outweight the extra "troubles".
--
Ticket URL: <https://trac.macports.org/ticket/33259#comment:52>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list