Changes between Version 187 and Version 188 of FAQ


Ignore:
Timestamp:
Apr 4, 2021, 9:52:27 AM (3 years ago)
Author:
jmroot (Joshua Root)
Comment:

add to from-source answer

Legend:

Unmodified
Added
Removed
Modified

  • FAQ

    v187 v188  
    77=== Does MacPorts always build from source? === #fromsource
    88
    9 MacPorts 2.0.0, released in 2011, added the ability to securely install ports from prebuilt binary archives. With a default configuration; you don't need to do anything to take advantage of this,
     9MacPorts 2.0.0, released in 2011, added the ability to securely install ports from prebuilt binary archives. With a default configuration, you don't need to do anything to take advantage of this,
    1010MacPorts will automatically install from an archive if one is available.
    1111
    … …  
    1515 * Archives are only prebuilt for a limited number of CPU architectures and OS versions.
    1616 * If you are using a custom value for any of the following macports.conf settings, the prebuilt archives are not compatible with your installation and will not be used: `prefix`, `applications_dir`, `frameworks_dir`, `cxx_stdlib`, `delete_la_files`
    17 
    18 These limitations could be avoided by using a custom archive site configured to suit your needs, rather than the official one, though of course someone still needs to build the archives. See [wiki:howto/ShareArchives2].
     17 * There is always some amount of time between when a Portfile is updated in git and when the Buildbot finishes building it and makes it available. This may be more noticeable if you sync your ports tree directly from git.
     18
     19Most of these limitations could be avoided by using a custom archive site configured to suit your needs, rather than the official one, though of course someone still needs to build the archives. See [wiki:howto/ShareArchives2].
    1920
    2021=== A port fails to build. What should I do? === #buildfails