Binary archives are never fetched for files in my local port repository

Joshua Root jmr at macports.org
Wed Sep 7 00:25:48 PDT 2016


On 2016-9-6 23:58 , Brandon Allbery wrote:
>
> On Tue, Sep 6, 2016 at 5:56 AM, Mojca Miklavec <mojca at macports.org
> <mailto:mojca at macports.org>> wrote:
>
>     I recently figured out that ports that I have in my local repository
>     are *never* updated from the binary archives, but always compiled from
>     sources. MacPorts doesn't even try to fetch the binary archives, it
>     goes straight to fetching the sources.
>
>
> Every repository has its own binary archives. After all, if you have it
> in your local repository, this is a pretty obvious indication that you
> are doing something different from the port in the main repo that has
> the binary archive, and that the binary archive for the main port
> therefore can't be considered compatible with your local port.

That's right. If you look at 
portarchivefetch::get_full_archive_sites_path in 
src/package1.0/portarchivefetch.tcl, it deliberately doesn't fall back 
to the default resources path.

If there is a _resources/port1.0/fetch/archive_sites.tcl in the repo, it 
will be used.

- Josh


More information about the macports-dev mailing list