… | |
… | |
2 | <!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
2 | <!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
3 | |
3 | |
4 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
4 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
5 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
5 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
6 | |
6 | |
7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.18 2004/01/08 14:23:17 swift Exp $ --> |
7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.22 2004/02/03 20:25:45 swift Exp $ --> |
8 | |
8 | |
9 | <sections> |
9 | <sections> |
10 | <section> |
10 | <section> |
11 | <title>Obtaining Package Information</title> |
11 | <title>Obtaining Package Information</title> |
12 | <subsection> |
12 | <subsection> |
… | |
… | |
128 | </p> |
128 | </p> |
129 | |
129 | |
130 | <p> |
130 | <p> |
131 | The other files are the <path>ChangeLog</path> (which contains a listing of all |
131 | The other files are the <path>ChangeLog</path> (which contains a listing of all |
132 | the changes done to the ebuilds), <path>Manifest</path> (which contains the |
132 | the changes done to the ebuilds), <path>Manifest</path> (which contains the |
133 | checksums and permissions of all the files in the directory) and |
133 | checksums and filesizes of all the files in the directory) and |
134 | <path>metadata.xml</path> (which contains more information about the package, |
134 | <path>metadata.xml</path> (which contains more information about the package, |
135 | such as the responsible development group -- called <e>herd</e> -- and a more |
135 | such as the responsible development group -- called <e>herd</e> -- and a more |
136 | extensive description). |
136 | extensive description). |
137 | </p> |
137 | </p> |
138 | |
138 | |
… | |
… | |
761 | to <e>ARCH</e> after being bugfree for a sufficient amount of time. |
761 | to <e>ARCH</e> after being bugfree for a sufficient amount of time. |
762 | </p> |
762 | </p> |
763 | |
763 | |
764 | <p> |
764 | <p> |
765 | Your system will use <e>ARCH</e> packages per default. If you want to live on |
765 | Your system will use <e>ARCH</e> packages per default. If you want to live on |
766 | the edge, don't mind having a broken package once in a while, and you like |
766 | the edge, don't mind having a broken package once in a while, know how to deal |
767 | submitting bugreports to <uri |
767 | with a broken system and you like submitting bugreports to <uri |
768 | link="http://bugs.gentoo.org">bugs.gentoo.org</uri>, then you can opt to use |
768 | link="http://bugs.gentoo.org">bugs.gentoo.org</uri>, then you can opt to use |
769 | <e>~ARCH</e> packages. To "move" your system to a <e>~ARCH</e>-using system, |
769 | <e>~ARCH</e> packages. To "move" your system to a <e>~ARCH</e>-using system, |
770 | edit the <c>ACCEPT_KEYWORDS</c> variable in <path>/etc/make.conf</path> so that |
770 | edit the <c>ACCEPT_KEYWORDS</c> variable in <path>/etc/make.conf</path> so that |
771 | it reads <e>~ARCH</e> (again: for x86-based systems: <e>~x86</e>, etc.). |
771 | it reads <e>~ARCH</e> (again: for x86-based systems: <e>~x86</e>, etc.). |
|
|
772 | </p> |
|
|
773 | |
|
|
774 | <p> |
|
|
775 | Note though that it is far from trivial (if even impossible) to go back to |
|
|
776 | <e>ARCH</e> from <e>~ARCH</e>. |
772 | </p> |
777 | </p> |
773 | |
778 | |
774 | <p> |
779 | <p> |
775 | If you want to update your system now, you will notice that <e>a lot</e> of |
780 | If you want to update your system now, you will notice that <e>a lot</e> of |
776 | packages will be updated! |
781 | packages will be updated! |
… | |
… | |
821 | the same format as is used in <path>/usr/portage/profiles/package.mask</path>). |
826 | the same format as is used in <path>/usr/portage/profiles/package.mask</path>). |
822 | </p> |
827 | </p> |
823 | |
828 | |
824 | <p> |
829 | <p> |
825 | Do <e>not</e> alter the <path>/usr/portage/profiles/package.mask</path> file as |
830 | Do <e>not</e> alter the <path>/usr/portage/profiles/package.mask</path> file as |
826 | all changes are undone the next time you update your Portage tree. |
831 | all changes are undone the next time you update your Portage tree. If you want |
|
|
832 | to hardmask a package create <path>/etc/portage/package.mask</path> and list the |
|
|
833 | package in it (use the same format as mentioned above). |
827 | </p> |
834 | </p> |
828 | |
835 | |
|
|
836 | <!-- |
829 | <p> |
837 | <p> |
830 | Another trick to circumvent the "masked package" problem is to install the |
838 | Another trick to circumvent the "masked package" problem is to install the |
831 | package using the full path. This will ignore both the <c>ACCEPT_KEYWORD</c> |
839 | package using the full path. This will ignore both the <c>ACCEPT_KEYWORD</c> |
832 | settings and the <path>package.mask</path> listing. |
840 | settings and the <path>package.mask</path> listing. |
833 | </p> |
841 | </p> |
834 | |
842 | |
835 | <pre caption="Installing a package without checking for stadium / masking"> |
843 | <pre caption="Installing a package without checking for stadium / masking"> |
836 | # <i>emerge /usr/portage/app-office/gnumeric/gnumeric-1.2.0.ebuild</i> |
844 | # <i>emerge /usr/portage/app-office/gnumeric/gnumeric-1.2.0.ebuild</i> |
837 | </pre> |
845 | </pre> |
|
|
846 | --> |
838 | |
847 | |
839 | </body> |
848 | </body> |
840 | </subsection> |
849 | </subsection> |
841 | <subsection> |
850 | <subsection> |
842 | <title>Blocked Packages</title> |
851 | <title>Blocked Packages</title> |