[MacPorts] #59787: Including a nonexistent portgroup should be an error

[MacPorts]

#59787: Including a nonexistent portgroup should be an error
------------------------+--------------------
 Reporter:  ryandesign  |      Owner:  (none)
     Type:  defect      |     Status:  new
 Priority:  Normal      |  Milestone:
Component:  base        |    Version:  2.6.2
 Keywords:              |       Port:
------------------------+--------------------
 When a Portfile includes a portgroup that does not exist, MacPorts prints
 a warning, then tries to build the port anyway, which can't possibly
 succeed. For example, I saw this when trying to use an old version of a
 portfile I grabbed from our history:

 {{{
 Warning: PortGroup python27 1.0 could not be located. python27-1.0.tcl
 does not exist.
 Warning: PortGroup python27 1.0 could not be located. python27-1.0.tcl
 does not exist.
 --->  Computing dependencies for py27-pylibelf
 --->  Fetching distfiles for py27-pylibelf
 --->  Verifying checksums for py27-pylibelf
 --->  Extracting py27-pylibelf
 --->  Applying patches to py27-pylibelf
 --->  Configuring py27-pylibelf
 Error: Failed to configure py27-pylibelf: configure failure: command
 execution failed
 }}}

 Including a nonexistent portgroup should be an error after which we stop,
 not a warning after which we try to proceed.

-- 
Ticket URL: <https://trac.macports.org/ticket/59787>
MacPorts <https://www.macports.org/>
Ports system for macOS