[MacPorts] #33259: cmake portgroup: out of source build option, possibly by default

[MacPorts]

#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 larryv@…):

 Replying to [comment:50 rjvbertin@…]:
 > I wasn't talking about the reason to use a portgroup, but to make OOS
 > builds the default in the cmake portgroup.

 I don’t see that this is any different. The point here is not necessarily
 to force all CMake ports to use out-of-source builds; it’s to eliminate
 the boilerplate that is currently required to do so.

 > I this case it should be sufficiently clear from looking (ok,
 > squinting hard) at the paths shown in the main.log Portfiles that just
 > do a standard cmake - build - install shouldn't run into any problems,
 > because cmake itself has no issues doing OOS builds.

 Sure, but I still don’t think that magically changing the build behavior
 from the other end of the repository (so to speak) is good practice.

 > Anyway, with GSoC coming up, why not tinker the portgroup inclusion
 > logic a bit? A change as proposed would fit in very well, I think,
 > with a scheme in which `Portgroup cmake 1` loads the most recent v1.x
 > portgroup, while `PortGroup cmake 1.x` would include the exact 1.x
 > version. That would allow portfiles that don't do anything "weird"
 > like copying things from ${build.dir} to ${destroot} can always use
 > the latest portgroup version, while ports with specific requirements
 > can specify what version they need. This seems so logical when
 > versions are already supported that the feature maybe exists already?

 It doesn’t; the version is used as-is. Better versioning is not a bad
 idea, but discuss it elsewhere. It’s a policy matter, not a technical one.
 (Implementing this would take literally ten minutes.)

-- 
Ticket URL: <https://trac.macports.org/ticket/33259#comment:51>
MacPorts <https://www.macports.org/>
Ports system for OS X