Changeset 2271 for trunk/www


Ignore:
Timestamp:
Mar 14, 2003, 10:37:31 AM (17 years ago)
Author:
jkh
Message:

Update the FAQ

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/www/faq.php

    r1354 r2271  
    33//
    44// File     : faq.php
    5 // Version  : $Id: faq.php,v 1.9 2002/12/08 16:13:57 landonf Exp $
     5// Version  : $Id: faq.php,v 1.10 2003/03/14 10:37:31 jkh Exp $
    66// Location : /projects/darwinports/faq.php
    77//
     
    101101<p><strong>Does darwinports also do package management?</strong></p>
    102102
    103 <p> At present, darwinports just builds software from scratch,
    104 installs it and records the installation so that you can ask
    105 darwinports to uninstall it again if necessary.  It will also create
    106 binary "snapshot" tarballs of a given port installation so that you
    107 can give these to someone else to simply unpack rather than having to
    108 build the ports themselves, but package management is something we've
    109 deliberately left for "phase II" of the project, where we'll probably
    110 adopt one of the existing package management systems and make
    111 darwinports simply generate those on demand.  Even with "proper
    112 package management", it will always be important to offer the
    113 capability of building things from source since something has to
    114 generate the packages for each release of the OS or the individual
    115 ports, and developers who are modifying system libraries or playing
    116 with different ways of building a given piece of software may find a
     103<p> Darwinports works by first building software, installing it
     104into a temporary directory (or "destroot") and then copying the
     105contents of that into its final $prefix resting place (typically
     106/opt/local).  It also records the installation with a "receipt"
     107so that you can ask darwinports to uninstall it again if necessary.
     108<p>Alternately, you can ask darwinports to build a packaged version
     109(pkg) of the software and install that with the standard installation tool
     110(Installer.app) on Mac OS X.  If the package has dependencies, you
     111can also build a multi-part package (mpkg) which contains them
     112as well, increasing convenience at the cost of disk space.  Whichever
     113type of Mac OS X package you install, you can also uninstall it with
     114the Uninstaller.app provided at <a href="http://packages.opendarwin.org/Applications">packages.opendarwin.org</a>.  For the future, there are plans to
     115support the RPM Package Manager (RPM) format as well.
     116
     117<p>It will always be important to offer the
     118capability of building things from source, of course, since something has to
     119generate packaged versions of these individual ports, and developers who
     120are modifying system libraries or playing
     121with different ways of building a given piece of software may also find a
    117122canned binary package to be insufficient for their needs. </p>
    118123
Note: See TracChangeset for help on using the changeset viewer.