Changeset 2472 for trunk/www


Ignore:
Timestamp:
Apr 15, 2003, 9:26:59 AM (17 years ago)
Author:
jkh
Message:

Merge copies of the FAQ

Location:
trunk/www
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/www/en/faq.php

    r1468 r2472  
    33//
    44// File     : faq.php
    5 // Version  : $Id: faq.php,v 1.11 2002/12/21 07:33:23 kevin Exp $
     5// Version  : $Id: faq.php,v 1.12 2003/04/15 09:26:59 jkh Exp $
    66// Location : /projects/darwinports/faq.php
    77//
     
    9191<p> It currently requires Mac OS X 10.2 (Jaguar) with the developer
    9292tools installed since that's the reference code base most of us are
    93 using.  There is also work planned to make it more compatible with
    94 10.1 (Puma) just as soon as we can identify all of the "variant"
    95 issues that need to be added to the various ports.  DarwinPorts does
    96 make provisions for OS version or architecture specific "variants" of
    97 a port and we intend to leverage this mechanism to support multiple OS
    98 versions and architectures (for Darwin/x86) in a fairly clean way.
     93using.  DarwinPorts does make provisions for OS version or architecture
     94specific "variants" of a port and we intend to leverage this mechanism to
     95support multiple OS versions and architectures (for Darwin/x86) in a
     96fairly clean way.
    9997</p>
    10098
    10199<p><strong>Does DarwinPorts also do package management?</strong></p>
    102100
    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
     101<p> DarwinPorts works by first building software, installing it
     102into a temporary directory (or "destroot") and then copying the
     103contents of that into its final $prefix resting place (typically
     104/opt/local).  It also records the installation with a "receipt"
     105so that you can ask DarwinPorts to uninstall it again if necessary.
     106<p>Alternately, you can ask DarwinPorts to build a packaged version
     107(pkg) of the software and install that with the standard installation tool
     108(Installer.app) on Mac OS X.  If the package has dependencies, you
     109can also build a multi-part package (mpkg) which contains them
     110as well, increasing convenience at the cost of disk space.  Whichever
     111type of Mac OS X package you install, you can also uninstall it with
     112the Uninstaller.app provided at <a href="http://packages.opendarwin.org/Applications">packages.opendarwin.org</a>.  For the future, there are plans to
     113support the RPM Package Manager (RPM) format as well.
     114
     115<p>It will always be important to offer the
     116capability of building things from source, of course, since something has to
     117generate packaged versions of these individual ports, and developers who
     118are modifying system libraries or playing
     119with different ways of building a given piece of software may also find a
    117120canned binary package to be insufficient for their needs. </p>
    118121
  • trunk/www/faq.php

    r2271 r2472  
    33//
    44// File     : faq.php
    5 // Version  : $Id: faq.php,v 1.10 2003/03/14 10:37:31 jkh Exp $
     5// Version  : $Id: faq.php,v 1.11 2003/04/15 09:26:58 jkh Exp $
    66// Location : /projects/darwinports/faq.php
    77//
    88
    99        include_once("$DOCUMENT_ROOT/includes/od_lib.inc.php");
    10         od_print_header("DarwinPorts FAQ", "en", "iso-8859-1", "");
     10        od_print_header("DarwinPorts FAQ", "en", "iso-8859-1", "", 0, "/projects/darwinports");
    1111?>
    1212
     
    2020<p>
    2121This document attempts to answer some frequently asked questions about
    22 darwinports.</p>
     22DarwinPorts.</p>
    2323
    2424<p><i>Author: Jordan K Hubbard</i></p>
    2525
    2626
    27 <p><strong>What IS darwinports?</strong></p>
     27<p><strong>What IS DarwinPorts?</strong></p>
    2828
    2929<p>
    30 darwinports is probably best described by comparison:  It's sort of like
     30DarwinPorts is probably best described by comparison:  It's sort of like
    3131the <a href="http://www.freebsd.org/ports">FreeBSD ports collection</a>
    3232or <a href="http://fink.sourceforge.net">fink</a> in that it automates
     
    3434tracks all dependency information for a given piece of software and knows
    3535how to make it build under Mac OS X and install it to a common
    36 location, meaning that software installed via darwinports doesn't
     36location, meaning that software installed via DarwinPorts doesn't
    3737simply scatter itself all over the system or require user knowledge
    3838of what to install in what order.
    3939</p>
    4040
    41 <p><strong>How is darwinports implemented?</strong></p>
     41<p><strong>How is DarwinPorts implemented?</strong></p>
    4242
    43 <p> The darwinports system is almost fully written in Tcl and designed
     43<p> The DarwinPorts system is almost fully written in Tcl and designed
    4444to be embedded into other applications, such as software browsing
    4545front-ends (like the work-in-progress
     
    5252meaning that as the system evolves, older things don't just break.</p>
    5353
    54 <p>Even though darwinports is written in Tcl, a user also does not need to
     54<p>Even though DarwinPorts is written in Tcl, a user also does not need to
    5555know Tcl in order to use the system or even to add new ports.  Port
    5656description files, though they are actually full Tcl programs in their
     
    5959</p>
    6060
    61 <p><strong>How does darwinports compare to FreeBSD ports?</strong></p>
     61<p><strong>How does DarwinPorts compare to FreeBSD ports?</strong></p>
    6262
    6363<p> FreeBSD ports is essentially implemented as some very impressive
     
    7070ports.</p>
    7171
    72 <p><strong>Why did darwinports start from scratch rather than adopting something like FreeBSD ports?</strong></p>
     72<p><strong>Why did DarwinPorts start from scratch rather than adopting something like FreeBSD ports?</strong></p>
    7373
    7474<p> Even discounting some of the limitations of FreeBSD ports
     
    7676rather more complex than it looks at first glance and there's always
    7777room for fresh approaches to the problem, which is what we set out to
    78 do with darwinports. There are certainly other systems, some of which
     78do with DarwinPorts. There are certainly other systems, some of which
    7979have already been mentioned, which have made their own attempts at
    8080solving this problem and there will likely be many more such systems
     
    8282everyone is rather like trying to find a single programming language
    8383which pleases everyone - it's more or less impossible.  We urge people
    84 to judge darwinports' design on its own merits and consider it a
     84to judge DarwinPorts' design on its own merits and consider it a
    8585parallel rather than a competing effort since there's more software
    8686out there than any one system can ever manage to encapsulate and
    8787automate. </p>
    8888
    89 <p><strong>What are the system requirements for Darwinports?</strong></p>
     89<p><strong>What are the system requirements for DarwinPorts?</strong></p>
    9090
    9191<p> It currently requires Mac OS X 10.2 (Jaguar) with the developer
    9292tools installed since that's the reference code base most of us are
    93 using.  There is also work planned to make it more compatible with
    94 10.1 (Puma) just as soon as we can identify all of the "variant"
    95 issues that need to be added to the various ports.  Darwinports does
    96 make provisions for OS version or architecture specific "variants" of
    97 a port and we intend to leverage this mechanism to support multiple OS
    98 versions and architectures (for Darwin/x86) in a fairly clean way.
     93using.  DarwinPorts does make provisions for OS version or architecture
     94specific "variants" of a port and we intend to leverage this mechanism to
     95support multiple OS versions and architectures (for Darwin/x86) in a
     96fairly clean way.
    9997</p>
    10098
    101 <p><strong>Does darwinports also do package management?</strong></p>
     99<p><strong>Does DarwinPorts also do package management?</strong></p>
    102100
    103 <p> Darwinports works by first building software, installing it
     101<p> DarwinPorts works by first building software, installing it
    104102into a temporary directory (or "destroot") and then copying the
    105103contents of that into its final $prefix resting place (typically
    106104/opt/local).  It also records the installation with a "receipt"
    107 so that you can ask darwinports to uninstall it again if necessary.
    108 <p>Alternately, you can ask darwinports to build a packaged version
     105so that you can ask DarwinPorts to uninstall it again if necessary.
     106<p>Alternately, you can ask DarwinPorts to build a packaged version
    109107(pkg) of the software and install that with the standard installation tool
    110108(Installer.app) on Mac OS X.  If the package has dependencies, you
     
    122120canned binary package to be insufficient for their needs. </p>
    123121
    124 <p><strong>Why does darwinports install everything into /opt/local by default?</strong></p>
     122<p><strong>Why does DarwinPorts install everything into /opt/local by default?</strong></p>
    125123
    126124<p>First, this location can be set to anything you like by editing
    127125/etc/ports/ports.conf so nothing is fixed in place.  Even the basic
    128 darwinports infrastructure, which installs into /opt/local by default,
     126DarwinPorts infrastructure, which installs into /opt/local by default,
    129127can be installed elsewhere by overriding the value of PREFIX on the
    130128command line (see the README file for details).  Second, we had to
     
    136134
    137135<p> See the <a
    138 href="http://www.opendarwin.org/projects/darwinports">darwinports</a>
     136href="http://www.opendarwin.org/projects/darwinports/en/">DarwinPorts</a>
    139137web page for information on checking the project out of CVS.  Once you
    140138get your hands on a copy, check out the top level README for
Note: See TracChangeset for help on using the changeset viewer.