On Tue, Jul 03, 2012 at 07:57:27PM -0400, Brandon Allbery wrote: > On Tue, Jul 3, 2012 at 7:38 PM, Gregory Seidman < > [email protected]> wrote: > > > On Tue, Jul 03, 2012 at 07:09:17PM -0400, Jeremy Lavergne wrote: > > > That's how it just works. > > > > Well, no, it doesn't just work. I want to issue a single port command, e.g. > > port upgrade outdated, and have it install binaries where available and > > install anything else from source. I want to *prefer* binaries without > > *restricting* to binaries. > > > > If that's not how it works by default for you, then you need to check your > /opt/local/etc/macports/macports.conf (there should be a stock one in the > same directory). Also, don't pass the -b or -s options to the "port" > command, which options force binary or source build modes on a particular > run. > > The default behavior is to attempt to download a prebuilt package, and if > that fails then do a source build.
If I don't specify -b, I always seem to build from source. What should I be looking for in the macports.conf? Also, is there any way to do something similar to port list outdated that will tell me whether a binary of a newer version is available? > brandon s allbery [email protected] --Greg _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
