Re: disable binary archive downloads for ports install
Two options. Per command: sudo port -s ... Globally in macports.conf: # When to build ports from source. Default is 'ifneeded', which downloads an # archive if available or builds from source otherwise. 'always' has the same # effect as -s on the command line, and 'never' is likewise the same as -b. #buildfromsourceifneeded On Jul 23, 2013, at 12:02 PM, Freek Dijkstra wrote: Is there a way to enforce building of a package, thus disabling downloads of precompiles binary archives? I expected that port build following by port install to work, but it still seems to download a precompiled version: ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: disable binary archive downloads for ports install
On Tue, Jul 23, 2013 at 06:02:49PM +0200, Freek Dijkstra wrote: Is there a way to enforce building of a package, thus disabling downloads of precompiles binary archives? Use port -s or set buildfromsource always in macports.conf PS: for those wondering why (as a precompiled package is usually the same as the one build locally): I use python32 variant +ucs4, and when compiling binary modules (such as py32-Pillow), the package is different based on the python variant. Apparently, the precompiled version is compile --without-wide-unicode (the ucs2 variant), while I'm using the ucs4 variant (--with-wide-unicode). That's a bug in the package you're trying to build and should be filed as such. -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: disable binary archive downloads for ports install
On 23-07-2013 18:04, Clemens Lang wrote: Is there a way to enforce building of a package, thus disabling downloads of precompiles binary archives? Use port -s or set buildfromsource always in macports.conf Thanks Clemens Jeremy! port -s worked like a charm. (I now see it is in the man page; I only checked 'port help install' and guide.macports.org, which didn't mention it either). PS: for those wondering why (as a precompiled package is usually the same as the one build locally): I use python32 variant +ucs4, and when compiling binary modules (such as py32-Pillow), the package is different based on the python variant. Apparently, the precompiled version is compile --without-wide-unicode (the ucs2 variant), while I'm using the ucs4 variant (--with-wide-unicode). That's a bug in the package you're trying to build and should be filed as such. I'm happy to file a bug report, but what is the proper behaviour in this case? The binary of the py32-Pillow package depends on a variant in another package (the python32 package). How should MacPorts distinguish between the two? Freek ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
