On Jun 23, 2015, at 3:51PM, Ryan Schmidt <ryandes...@macports.org> wrote:
>
>> On Jun 23, 2015, at 5:48 PM, Lawrence Velázquez <lar...@macports.org> wrote:
>>
>> On Jun 23, 2015, at 5:21 PM, Ryan Schmidt <ryandes...@macports.org> wrote:
>>
>>> Yes, but then we get into the problem of order of inclusion. If the github
>>> portgroup sets default master_sites, and the python portgroup sets default
>>> master_sites, which one gets used depends on the order you include the
>>> portgroups, which isn't great.
>>
>> Another possibility could be to establish some sort of precedence guidelines.
>>
>> For instance, I think it's reasonable to assume that a port that includes
>> github-1.1 _really_ intends to fetch from GitHub, while a port that uses
>> python-1.1 may or may not want to fetch from PyPI. So python-1.1 would defer
>> to github-1.1.
>
> Mmm, it should be possible to write that.
>
>
>>> I planned to make the default for github.project be ${name} and the default
>>> for github.version be ${version} (since currently we do the reverse of
>>> that).
>>
>> Wouldn't all the portgroup's settings take effect by default then? What
>> would be your trigger?
>
> Setting github.author would be the trigger for setting the defaults for
> github.project, github.version, and others.
>
If the python portgroup triggers off of python.versions and the github
portgroup triggers off of github.author, does this introduce the same problem
as the order of the PortGroup include statements (this particular point of
PortGroup order was raised on the pypi thread).
-Sterling
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
