Avoid mirroring a distfile
Bradley Giesbrecht
pixilla at macports.org
Thu Feb 2 18:13:03 PST 2012
On Feb 2, 2012, at 4:27 PM, Jeremy Lavergne wrote:
>> I'm not sure how `port list` handles subports.
>
> Hope this helps shed some high level light.
>
> `port list` goes through everything in the PortIndex. The PortIndex is comprised of the results of parsing each Portfile, including multiple passes on a single Portfile to generate each subport as well. Subports really just save maintainer programming time and they don't really impact much else. Here's an example of all the py*-requests packages, which are all generated from a single Portfile:
>
> py-requests @0.8.4 python/py-requests
> py26-requests @0.8.4 python/py-requests
> py27-requests @0.8.4 python/py-requests
>
> As you can see, each port that's computed from the subports in a Portfile comes from the same $portpath (which is impacted by the per-commit mirroring you mentioned). Subports from the same Portfile also share the same Portfile and sometimes the same distfile, but otherwise they're considered different ports.
We would not want to make a distributable port non-distributable because we chose to add a subport that is not distributable.
I think these replies are saying this is a non-issue.
Regards,
Bradley Giesbrecht (pixilla)
More information about the macports-dev
mailing list