[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 rjvbertin@…):

 Replying to [comment:49 larryv@…]:

 > > which kind of goes against the very reasons OOS builds were made the
 > > default
 >
 > I don’t agree. The point of portgroups is to cut down on portfile
 boilerplate, not necessarily to reduce maintainer effort.

 I wasn't talking about the reason to use a portgroup, but to make OOS
 builds the default in the cmake portgroup.

 > Also: Given that this modification would change the default build
 behavior, I think it’d be a good thing to require portfiles to be updated
 for it. It’s confusing when a port’s behavior mysteriously changes because
 of portgroup action-at-a-distance, especially if it breaks. This happens
 all too often, and it can be difficult to debug.

 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.

 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?

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