Changes between Version 2 and Version 3 of MacPortsRenaming


Ignore:
Timestamp:
Jun 1, 2007, 5:49:55 AM (17 years ago)
Author:
jmpp@…
Comment:

Minor corrections

Legend:

Unmodified
Added
Removed
Modified

  • MacPortsRenaming

    v2 v3  
    88 * internal routines naming, e.g. renaming `dportinit` to `mportinit` and many other examples in this category;
    99 * installation paths, e.g. going from a `${prefix}/share/darwinports` MacPorts base installation path at the host level to `${prefix}/share/macports`;
    10  * distribution means, e.g. by using the `rsync.macports.org` server for source and ports distribution and updating corresponding options in configuration files of existing installations to reflect this;
     10 * distribution means, e.g. by using the `rsync.macports.org` server for source and ports distribution and updating corresponding options in configuration files in existing installations to reflect this;
    1111 * ...
    1212
    … …  
    2323}}}
    2424
    25 The last entry in the list above represents an important and delicate move, since MacPorts operates inside the `/opt/local/var/db/dports` directory for many of its internal operations, like fetching Portfiles and building ports, among many other activities. Previously, MacPorts would fetch its own sources and the ports tree through the `selfupdate` and/or `sync` routines into a `/opt/local/var/db/dports/sources/rsync.<rsync_server>_<rsync_module>` skeleton, replacing dots and other characters in server/module names with `_` in some parts of the resulting directory name; therefore the most common and default paths for the rsync based MacPorts sources and ports tree would look like:
     25The last entry in the list above represents an important and delicate move, since MacPorts operates inside the `/opt/local/var/db/dports` directory for many of its internal operations, like fetching Portfiles and building ports, among many other activities. Previously, MacPorts would fetch its own sources and the ports tree through the `selfupdate` and/or `sync` routines into a `/opt/local/var/db/dports/sources/rsync.<rsync_server>_<rsync_module>` skeleton, replacing dots and other characters in server/module names with `_` in some parts of the resulting directory name. Therefore the most common and default paths for the rsync based MacPorts sources and ports tree would look like:
    2626
    2727{{{
    … …  
    3030}}}
    3131
    32 `selfupdate` and `sync` routines in this branch, however, have been upgraded to work with a much more flexible and cleaner skeleton: sources are now fetched into a `/opt/local/var/macports/sources/<server>/<rsync_module>` hierarchy. This may not seem like much at first, but closer inspection reveals this approach allows room to grow in every custom way users might need while also preserving a sense of order. Default paths will now look like:
     32`selfupdate` and `sync` routines in this branch, however, have been upgraded to work with a much more flexible and cleaner skeleton: sources are now fetched into a `/opt/local/var/macports/sources/<server>/<rsync_module>` hierarchy. This may not seem like much at first, but closer inspection reveals this approach allows room to grow in every custom way users might need, while also preserving a sense of order. Default paths will now look like:
    3333
    3434{{{
    … …  
    5151}}}
    5252
    53 MacPorts users catering to the varied needs of clients on large networks, who might have needs for multiple ports trees would instantly see the benefit in this approach:
     53MacPorts users catering to the varied needs of clients on large networks, who might have needs for multiple ports trees, would instantly see the benefits of this approach:
    5454
    5555{{{