pkgsrc-Changes-HG archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
[pkgsrc/trunk]: pkgsrc/doc/guide/files Avoid extra whitespace in <para>. Use ...
details: https://anonhg.NetBSD.org/pkgsrc/rev/b6d4fd804804
branches: trunk
changeset: 518476:b6d4fd804804
user: wiz <wiz%pkgsrc.org@localhost>
date: Sun Sep 10 19:30:56 2006 +0000
description:
Avoid extra whitespace in <para>. Use more macros.
diffstat:
doc/guide/files/platforms.xml | 624 +++++++++++++++++++++---------------------
1 files changed, 312 insertions(+), 312 deletions(-)
diffs (truncated from 927 to 300 lines):
diff -r 767d8be12de2 -r b6d4fd804804 doc/guide/files/platforms.xml
--- a/doc/guide/files/platforms.xml Sun Sep 10 19:29:52 2006 +0000
+++ b/doc/guide/files/platforms.xml Sun Sep 10 19:30:56 2006 +0000
@@ -1,4 +1,4 @@
-<!-- $NetBSD: platforms.xml,v 1.38 2006/09/02 11:26:16 schwarz Exp $ -->
+<!-- $NetBSD: platforms.xml,v 1.39 2006/09/10 19:30:56 wiz Exp $ -->
<chapter id="platforms">
<title>Using pkgsrc on systems other than &os;</title>
@@ -214,31 +214,31 @@
<para>Installing the bootstrap kit from source should be as simple as:</para>
<screen>
-&rprompt; <userinput>env CVS_RSH=ssh cvs -d anoncvs%anoncvs.NetBSD.org@localhost:/cvsroot checkout pkgsrc</userinput>
-&rprompt; <userinput>cd pkgsrc/bootstrap</userinput>
-&rprompt; <userinput>./bootstrap</userinput></screen>
+ &rprompt; <userinput>env CVS_RSH=ssh cvs -d anoncvs%anoncvs.NetBSD.org@localhost:/cvsroot checkout pkgsrc</userinput>
+ &rprompt; <userinput>cd pkgsrc/bootstrap</userinput>
+ &rprompt; <userinput>./bootstrap</userinput></screen>
<para>See <xref linkend="getting"/> for other ways to get
- pkgsrc before bootstrapping. The given
- <command>bootstrap</command> command will use the defaults of
- <filename>/usr/pkg</filename> for the
- <emphasis>prefix</emphasis> where programs will be installed in,
- and <filename>/var/db/pkg</filename> for the package database
- directory where pkgsrc will do its internal bookkeeping.
- However, these can also be set using command-line
- arguments.</para>
+ pkgsrc before bootstrapping. The given
+ <command>bootstrap</command> command will use the defaults of
+ <filename>/usr/pkg</filename> for the
+ <emphasis>prefix</emphasis> where programs will be installed in,
+ and <filename>/var/db/pkg</filename> for the package database
+ directory where pkgsrc will do its internal bookkeeping.
+ However, these can also be set using command-line
+ arguments.</para>
<para>Binary packages for the pkgsrc tools and an initial set of packages is
- available for supported platforms. An up-to-date list of these can be
- found on <ulink url="http://www.pkgsrc.org/";>www.pkgsrc.org</ulink>.
- Note that this only works for privileged builds that install
- into <filename>/usr/pkg</filename>.</para>
+ available for supported platforms. An up-to-date list of these can be
+ found on <ulink url="http://www.pkgsrc.org/";>www.pkgsrc.org</ulink>.
+ Note that this only works for privileged builds that install
+ into <filename>/usr/pkg</filename>.</para>
<note>
- <para>The bootstrap installs a <command>bmake</command> tool.
- Use this <command>bmake</command> when building via pkgsrc.
- For examples in this guide, use <command>bmake</command>
- instead of <quote>make</quote>.</para>
+ <para>The bootstrap installs a <command>bmake</command> tool.
+ Use this <command>bmake</command> when building via pkgsrc.
+ For examples in this guide, use <command>bmake</command>
+ instead of <quote>make</quote>.</para>
</note>
</sect1>
@@ -257,17 +257,17 @@
partition</link>.</para>
<para>Before you start, you will need to download and install the Mac OS X Developer
- Tools from Apple's Developer Connection. See <ulink
- url="http://developer.apple.com/macosx/";>http://developer.apple.com/macosx/</ulink>
- for details. Also, make sure you install X11 for Mac OS X and the X11 SDK
- from <ulink
- url="http://www.apple.com/macosx/x11/download/";>http://www.apple.com/macosx/x11/download/</ulink>
- if you intend to build packages that use the X11 Window System.</para>
+ Tools from Apple's Developer Connection. See <ulink
+ url="http://developer.apple.com/macosx/";>http://developer.apple.com/macosx/</ulink>
+ for details. Also, make sure you install X11 for Mac OS X and the X11 SDK
+ from <ulink
+ url="http://www.apple.com/macosx/x11/download/";>http://www.apple.com/macosx/x11/download/</ulink>
+ if you intend to build packages that use the X11 Window System.</para>
<para>If you already have a UFS partition, or have a spare partition
- that you can format as UFS, it is recommended to use that instead of
- the disk image. It'll be somewhat faster and will mount automatically
- at boot time, where you must manually mount a disk image.</para>
+ that you can format as UFS, it is recommended to use that instead of
+ the disk image. It'll be somewhat faster and will mount automatically
+ at boot time, where you must manually mount a disk image.</para>
<note>
<para>You cannot use an ordinary HFS+ file system for pkgsrc, because pkgsrc currently
@@ -296,77 +296,76 @@
<title>Using a UFS partition</title>
<para>By default, <filename>/usr</filename> will be on your root file
- system, normally HFS+. It is possible to use the default
- <emphasis>prefix</emphasis> of <filename>/usr/pkg</filename>
- by symlinking <filename>/usr/pkg</filename> to a directory on a UFS
- file system. Obviously, another symlink is required if you want to
- place the package database directory outside the
- <emphasis>prefix</emphasis>. e.g.</para>
+ system, normally HFS+. It is possible to use the default
+ <emphasis>prefix</emphasis> of <filename>/usr/pkg</filename>
+ by symlinking <filename>/usr/pkg</filename> to a directory on a UFS
+ file system. Obviously, another symlink is required if you want to
+ place the package database directory outside the
+ <emphasis>prefix</emphasis>. e.g.</para>
<screen>&rprompt; <userinput>./bootstrap --pkgdbdir /usr/pkg/pkgdb</userinput></screen>
<para>If you created your partitions at the time of installing Mac OS X
- and formatted the target partition as UFS, it should automatically
- mount on <filename>/Volumes/<volume name></filename> when the
- machine boots. If you are (re)formatting a partition as UFS, you need
- to ensure that the partition map correctly reflects
- <quote>Apple_UFS</quote> and not <quote>Apple_HFS</quote>.</para>
+ and formatted the target partition as UFS, it should automatically
+ mount on <filename>/Volumes/<volume name></filename> when the
+ machine boots. If you are (re)formatting a partition as UFS, you need
+ to ensure that the partition map correctly reflects
+ <quote>Apple_UFS</quote> and not <quote>Apple_HFS</quote>.</para>
<para>The problem is that none of the disk tools will let you touch a
- disk that is booted from. You can unmount the partition, but even if
- you newfs it, the partition type will be incorrect and the
- automounter won't mount it. It can be mounted manually, but it won't
- appear in Finder.</para>
+ disk that is booted from. You can unmount the partition, but even if
+ you newfs it, the partition type will be incorrect and the
+ automounter won't mount it. It can be mounted manually, but it won't
+ appear in Finder.</para>
<para>You'll need to boot off of the OS X Installation (User) CD. When
- the Installation program starts, go up to the menu and select Disk
- Utility. Now, you will be able to select the partition you want
- to be UFS, and Format it Apple UFS. Quit the Disk Utility, quit the
- installer which will reboot your machine. The new UFS file system
- will appear in Finder.</para>
+ the Installation program starts, go up to the menu and select Disk
+ Utility. Now, you will be able to select the partition you want
+ to be UFS, and Format it Apple UFS. Quit the Disk Utility, quit the
+ installer which will reboot your machine. The new UFS file system
+ will appear in Finder.</para>
<para>Be aware that the permissions on the new file system will be writable
- by root only.</para>
+ by root only.</para>
<para>This note is as of 10.2 (Jaguar) and applies to earlier versions.
- Hopefully Apple will fix Disk Utility in 10.3 (Panther).</para>
+ Hopefully Apple will fix Disk Utility in 10.3 (Panther).</para>
</sect3>
</sect2>
<sect2 id="freebsd">
<title>FreeBSD</title>
- <para>
- FreeBSD 4.7 and 5.0 have been tested and are supported, other versions
- may work.</para>
+ <para>FreeBSD 4.7 and 5.0 have been tested and are supported,
+ other versions may work.</para>
<para>Care should be taken so that the tools that this kit installs do not conflict
- with the FreeBSD userland tools. There are several steps:</para>
+ with the FreeBSD userland tools. There are several steps:</para>
<orderedlist>
<listitem>
<para>FreeBSD stores its ports pkg database in
- <filename>/var/db/pkg</filename>. It is therefore
- recommended that you choose a different location (e.g.
- <filename>/usr/pkgdb</filename>) by
- using the --pkgdbdir option to the bootstrap script.</para>
+ <filename>/var/db/pkg</filename>. It is therefore
+ recommended that you choose a different location (e.g.
+ <filename>/usr/pkgdb</filename>) by
+ using the --pkgdbdir option to the bootstrap script.</para>
</listitem>
<listitem>
<para>If you do not intend to use the FreeBSD ports tools, it's probably a
- good idea to move them out of the way to avoid confusion, e.g.</para>
+ good idea to move them out of the way to avoid confusion, e.g.</para>
<screen>&rprompt; <userinput>cd /usr/sbin</userinput>
-&rprompt; <userinput>mv pkg_add pkg_add.orig</userinput>
-&rprompt; <userinput>mv pkg_create pkg_create.orig</userinput>
-&rprompt; <userinput>mv pkg_delete pkg_delete.orig</userinput>
-&rprompt; <userinput>mv pkg_info pkg_info.orig</userinput></screen>
-</listitem>
+ &rprompt; <userinput>mv pkg_add pkg_add.orig</userinput>
+ &rprompt; <userinput>mv pkg_create pkg_create.orig</userinput>
+ &rprompt; <userinput>mv pkg_delete pkg_delete.orig</userinput>
+ &rprompt; <userinput>mv pkg_info pkg_info.orig</userinput></screen>
+ </listitem>
<listitem>
<para>An example <filename>/etc/mk.conf</filename> file will be placed in
- <filename>/etc/mk.conf.example</filename> file
- when you use the bootstrap script.</para>
+ <filename>/etc/mk.conf.example</filename> file
+ when you use the bootstrap script.</para>
</listitem>
</orderedlist>
</sect2>
@@ -375,21 +374,21 @@
<title>Interix</title>
<para>Interix is a POSIX-compatible subsystem for the Windows NT kernel,
- providing a Unix-like environment with a tighter kernel integration than
- available with Cygwin. It is part of the Windows Services for Unix
- package, available for free for any licensed copy of Windows 2000, XP
- (not including XP Home), or 2003. SFU can be downloaded from <ulink
- url="http://www.microsoft.com/windows/sfu/";>http://www.microsoft.com/windows/sfu/</ulink>.</para>
+ providing a Unix-like environment with a tighter kernel integration than
+ available with Cygwin. It is part of the Windows Services for Unix
+ package, available for free for any licensed copy of Windows 2000, XP
+ (not including XP Home), or 2003. SFU can be downloaded from <ulink
+ url="http://www.microsoft.com/windows/sfu/";>http://www.microsoft.com/windows/sfu/</ulink>.</para>
<para>Services for Unix 3.5, current as of this writing, has been tested. 3.0
- or 3.1 may work, but are not officially supported. (The main difference
- in 3.0/3.1 is lack of pthreads.)</para>
+ or 3.1 may work, but are not officially supported. (The main difference
+ in 3.0/3.1 is lack of pthreads.)</para>
<sect3 id="platform.interix-sfu-install">
<title>When installing Interix/SFU</title>
<para>At an absolute minimum, the following packages must be installed from
- the Windows Services for Unix 3.5 distribution in order to use pkgsrc:</para>
+ the Windows Services for Unix 3.5 distribution in order to use pkgsrc:</para>
<itemizedlist>
<listitem><para>Utilities -> Base Utilities</para></listitem>
@@ -399,28 +398,28 @@
</itemizedlist>
<para>When using pkgsrc on Interix, DO NOT install the Utilities subcomponent
- "UNIX Perl". That is Perl 5.6 without shared module support, installed to
- /usr/local, and will only cause confusion. Instead, install Perl 5.8 from
- pkgsrc (or from a binary package).</para>
+ "UNIX Perl". That is Perl 5.6 without shared module support, installed to
+ /usr/local, and will only cause confusion. Instead, install Perl 5.8 from
+ pkgsrc (or from a binary package).</para>
<para>The Remote Connectivity subcomponent "Windows Remote Shell Service" does
- not need to be installed, but Remote Connectivity itself should be
- installed in order to have a working inetd.</para>
+ not need to be installed, but Remote Connectivity itself should be
+ installed in order to have a working inetd.</para>
<para>During installation you may be asked whether to enable setuid
- behavior for Interix programs, and whether to make pathnames default to
- case-sensitive. Setuid should be enabled, and case-sensitivity MUST be
- enabled. (Without case-sensitivity, a large number of packages including
- perl will not build.)</para>
+ behavior for Interix programs, and whether to make pathnames default to
+ case-sensitive. Setuid should be enabled, and case-sensitivity MUST be
+ enabled. (Without case-sensitivity, a large number of packages including
+ perl will not build.)</para>
<para>NOTE: Newer Windows service packs change the way binary execution
- works (via the Data Execution Prevention feature). In order to use
- pkgsrc and other gcc-compiled binaries reliably, a hotfix containing
- POSIX.EXE, PSXDLL.DLL, PSXRUN.EXE, and PSXSS.EXE (899522 or newer)
- must be installed. Hotfixes are available from Microsoft through a
- support contract; however, a NetBSD developer has made most Interix
- hotfixes available for personal use from <ulink
- url="http://www.duh.org/interix/hotfixes.php";>http://www.duh.org/interix/hotfixes.php</ulink>.</para>
+ works (via the Data Execution Prevention feature). In order to use
+ pkgsrc and other gcc-compiled binaries reliably, a hotfix containing
+ POSIX.EXE, PSXDLL.DLL, PSXRUN.EXE, and PSXSS.EXE (899522 or newer)
+ must be installed. Hotfixes are available from Microsoft through a
+ support contract; however, a NetBSD developer has made most Interix
+ hotfixes available for personal use from <ulink
+ url="http://www.duh.org/interix/hotfixes.php";>http://www.duh.org/interix/hotfixes.php</ulink>.</para>
</sect3>
@@ -428,23 +427,23 @@
<title>What to do if Interix/SFU is already installed</title>
<para>If SFU is already installed and you wish to alter these settings to work
- with pkgsrc, note the following things.</para>
+ with pkgsrc, note the following things.</para>
<itemizedlist>
<listitem>
<para>To uninstall UNIX Perl, use Add/Remove Programs, select Microsoft
- Windows Services for UNIX, then click Change. In the installer, choose
- Add or Remove, then uncheck Utilities->UNIX Perl.</para>
+ Windows Services for UNIX, then click Change. In the installer, choose
+ Add or Remove, then uncheck Utilities->UNIX Perl.</para>
</listitem>
<listitem>
<para>To enable case-sensitivity for the file system, run REGEDIT.EXE, and
- change the following registry key:</para>
+ change the following registry key:</para>
<para>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\kernel</para>
<para>Set the DWORD value "obcaseinsensitive" to 0; then reboot.</para>
</listitem>
<listitem>
Home |
Main Index |
Thread Index |
Old Index