[MacPorts] #49925: KF5 : PortGroup and initial ports (frameworks)

[MacPorts]

#49925: KF5 : PortGroup and initial ports (frameworks)
--------------------------+------------------
  Reporter:  rjvbertin@…  |      Owner:  mk@…
      Type:  submission   |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:
      Port:               |
--------------------------+------------------

Comment (by rjvbertin@…):

 Replying to [comment:34 mk@…]:

 > Why did you split off {{{kf5-frameworks-1.0.tcl}}} from
 {{{kf5-1.1.tcl}}} ?

 I did some tinkering on a port (QupZilla) that has the option to use a
 specific KF5 framework, but that really cannot be called a "KF5
 application". Specifically, it doesn't use cmake for configuring, but it
 also has no interest in the majority of other things that the KF5
 PortGroup does. I had to introduce yet another control variable for the
 PortGroup, and use 3 of them from QupZilla's Portfile in order to be able
 to include the KF5 PortGroup without unwanted side-effects. All for just
 being able to declare a dependency on a single KF5 framework.

 So I decided to create a special PortGroup that provides only the
 dependency features and that can be included without any side-effects.

 I'm not aware of some guideline against justifiable PortGroups, is there?

 > Strange, I never copied the latter into my MacPorts installation's
 portgroup folder... X-O
 > How come it worked anyways?

 Simple: all KF5 ports are in the same tree as kf5-1.0.tcl so the file was
 always found. You only need to copy over PortGroup files if they are to be
 used by ports in a different ports tree. Like for instance if you want to
 use port:qt5-kde with mainstream Qt5 ports.

-- 
Ticket URL: <https://trac.macports.org/ticket/49925#comment:35>
MacPorts <https://www.macports.org/>
Ports system for the Mac operating system