Add additional recommendations for using ports over packages.
Warn about installing all the ports when you might install two ports that overwrite one another's files. Submitted by: Salvo Bartolotta <bartequi@neomedia.it>
This commit is contained in:
Nik Clayton
parent
e8e0d365eb
commit
5eda1065fc
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=7120
4 changed files with 100 additions and 12 deletions
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.93 2000/04/10 17:57:14 asami Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.94 2000/04/18 04:19:28 obrien Exp $
|
||||
-->
|
||||
|
||||
<chapter id="ports">
|
||||
|
|
@ -419,10 +419,23 @@ Receiving xchat-1.3.8.tar.bz2 (305543 bytes): 100%
|
|||
compiled that differ from the person who did the
|
||||
package—some people have strong views on what
|
||||
optimization settings should be used, whether to build
|
||||
debug versions and then strip them or not, etc.,
|
||||
etc..</para>
|
||||
debug versions and then strip them or not, and so on.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Packages are normally built with quite conservative
|
||||
settings. If a port has a compilation option to use code
|
||||
for a specific processor, or a particular add-on board you
|
||||
can enable this yourself in the port, without the people
|
||||
making the package having to produce many, many different
|
||||
packaged versions.</para>
|
||||
|
||||
<para>The most obvious exception to this rule is paper sizes.
|
||||
If a package can be provided with default support for
|
||||
different paper sizes we will often provide multiple
|
||||
packages, one per paper size.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Some people like having code around, so they can read
|
||||
it if they get bored, hack it, borrow from it (license
|
||||
|
|
@ -701,6 +714,10 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
|
|||
the source directory and inspect the Makefiles by hand, but
|
||||
this can get tedious if the source has lots of
|
||||
sub-directories, each with their own Makefiles.</para>
|
||||
|
||||
<para>The default FreeBSD compiler options are quite conservative,
|
||||
so if you have not changed them you should not have any
|
||||
problems.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
@ -829,6 +846,11 @@ arcade game.</screen>
|
|||
|
||||
<screen>&prompt.root; <userinput>cd /usr/ports</userinput>
|
||||
&prompt.root; <userinput>make install</userinput></screen>
|
||||
|
||||
<para>Be careful, as some ports may install files with the same
|
||||
name. If you install two graphics ports and they both install
|
||||
<filename>/usr/local/bin/plot</filename> then you will obviously
|
||||
have problems.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.93 2000/04/10 17:57:14 asami Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.94 2000/04/18 04:19:28 obrien Exp $
|
||||
-->
|
||||
|
||||
<chapter id="ports">
|
||||
|
|
@ -419,10 +419,23 @@ Receiving xchat-1.3.8.tar.bz2 (305543 bytes): 100%
|
|||
compiled that differ from the person who did the
|
||||
package—some people have strong views on what
|
||||
optimization settings should be used, whether to build
|
||||
debug versions and then strip them or not, etc.,
|
||||
etc..</para>
|
||||
debug versions and then strip them or not, and so on.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Packages are normally built with quite conservative
|
||||
settings. If a port has a compilation option to use code
|
||||
for a specific processor, or a particular add-on board you
|
||||
can enable this yourself in the port, without the people
|
||||
making the package having to produce many, many different
|
||||
packaged versions.</para>
|
||||
|
||||
<para>The most obvious exception to this rule is paper sizes.
|
||||
If a package can be provided with default support for
|
||||
different paper sizes we will often provide multiple
|
||||
packages, one per paper size.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Some people like having code around, so they can read
|
||||
it if they get bored, hack it, borrow from it (license
|
||||
|
|
@ -701,6 +714,10 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
|
|||
the source directory and inspect the Makefiles by hand, but
|
||||
this can get tedious if the source has lots of
|
||||
sub-directories, each with their own Makefiles.</para>
|
||||
|
||||
<para>The default FreeBSD compiler options are quite conservative,
|
||||
so if you have not changed them you should not have any
|
||||
problems.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
@ -829,6 +846,11 @@ arcade game.</screen>
|
|||
|
||||
<screen>&prompt.root; <userinput>cd /usr/ports</userinput>
|
||||
&prompt.root; <userinput>make install</userinput></screen>
|
||||
|
||||
<para>Be careful, as some ports may install files with the same
|
||||
name. If you install two graphics ports and they both install
|
||||
<filename>/usr/local/bin/plot</filename> then you will obviously
|
||||
have problems.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.93 2000/04/10 17:57:14 asami Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.94 2000/04/18 04:19:28 obrien Exp $
|
||||
-->
|
||||
|
||||
<chapter id="ports">
|
||||
|
|
@ -419,10 +419,23 @@ Receiving xchat-1.3.8.tar.bz2 (305543 bytes): 100%
|
|||
compiled that differ from the person who did the
|
||||
package—some people have strong views on what
|
||||
optimization settings should be used, whether to build
|
||||
debug versions and then strip them or not, etc.,
|
||||
etc..</para>
|
||||
debug versions and then strip them or not, and so on.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Packages are normally built with quite conservative
|
||||
settings. If a port has a compilation option to use code
|
||||
for a specific processor, or a particular add-on board you
|
||||
can enable this yourself in the port, without the people
|
||||
making the package having to produce many, many different
|
||||
packaged versions.</para>
|
||||
|
||||
<para>The most obvious exception to this rule is paper sizes.
|
||||
If a package can be provided with default support for
|
||||
different paper sizes we will often provide multiple
|
||||
packages, one per paper size.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Some people like having code around, so they can read
|
||||
it if they get bored, hack it, borrow from it (license
|
||||
|
|
@ -701,6 +714,10 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
|
|||
the source directory and inspect the Makefiles by hand, but
|
||||
this can get tedious if the source has lots of
|
||||
sub-directories, each with their own Makefiles.</para>
|
||||
|
||||
<para>The default FreeBSD compiler options are quite conservative,
|
||||
so if you have not changed them you should not have any
|
||||
problems.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
@ -829,6 +846,11 @@ arcade game.</screen>
|
|||
|
||||
<screen>&prompt.root; <userinput>cd /usr/ports</userinput>
|
||||
&prompt.root; <userinput>make install</userinput></screen>
|
||||
|
||||
<para>Be careful, as some ports may install files with the same
|
||||
name. If you install two graphics ports and they both install
|
||||
<filename>/usr/local/bin/plot</filename> then you will obviously
|
||||
have problems.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.93 2000/04/10 17:57:14 asami Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.94 2000/04/18 04:19:28 obrien Exp $
|
||||
-->
|
||||
|
||||
<chapter id="ports">
|
||||
|
|
@ -419,10 +419,23 @@ Receiving xchat-1.3.8.tar.bz2 (305543 bytes): 100%
|
|||
compiled that differ from the person who did the
|
||||
package—some people have strong views on what
|
||||
optimization settings should be used, whether to build
|
||||
debug versions and then strip them or not, etc.,
|
||||
etc..</para>
|
||||
debug versions and then strip them or not, and so on.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Packages are normally built with quite conservative
|
||||
settings. If a port has a compilation option to use code
|
||||
for a specific processor, or a particular add-on board you
|
||||
can enable this yourself in the port, without the people
|
||||
making the package having to produce many, many different
|
||||
packaged versions.</para>
|
||||
|
||||
<para>The most obvious exception to this rule is paper sizes.
|
||||
If a package can be provided with default support for
|
||||
different paper sizes we will often provide multiple
|
||||
packages, one per paper size.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Some people like having code around, so they can read
|
||||
it if they get bored, hack it, borrow from it (license
|
||||
|
|
@ -701,6 +714,10 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
|
|||
the source directory and inspect the Makefiles by hand, but
|
||||
this can get tedious if the source has lots of
|
||||
sub-directories, each with their own Makefiles.</para>
|
||||
|
||||
<para>The default FreeBSD compiler options are quite conservative,
|
||||
so if you have not changed them you should not have any
|
||||
problems.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
@ -829,6 +846,11 @@ arcade game.</screen>
|
|||
|
||||
<screen>&prompt.root; <userinput>cd /usr/ports</userinput>
|
||||
&prompt.root; <userinput>make install</userinput></screen>
|
||||
|
||||
<para>Be careful, as some ports may install files with the same
|
||||
name. If you install two graphics ports and they both install
|
||||
<filename>/usr/local/bin/plot</filename> then you will obviously
|
||||
have problems.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue