Hi René,
On 07 Jul 2015, at 23:22 , René J.V. Bertin <rjvber...@gmail.com> wrote:
> A specific file, either one installed anyway by Qt but in a location specific
> to qt5-kde,
> or something like a README or stub file that's specific to the port.
ah, ok, so it would be up to you to create this specific file for the qt5-kde
port…
> PortGroup files can and do use PortGroup commands to include other port
> groups (ex: the qmake PortGroups).
I know.
> then a port that wants qt5-kde as its default dependency could do
>
> {{{
> set qt5.prefer_kde yes
> PortGroup qt5 1.0
> }}}
Hmmm, interesting…
> Anyway, yes, this could benefit from some discussion, because evidently one
> would have to
> duplicate at least the path: style dependency declarations in both the 2
> actual payload
> PortGroups, or else move it into the generic/omnipotent PortGroup …
Yes, this needs careful discussing, as quite a few projects will be hit by this
in the future.
Greets,
Marko
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
