1 |
robbat2 07/11/28 20:22:39 |
2 |
|
3 |
Modified: cascading-profiles.xml |
4 |
Log: |
5 |
Fix URLs for new packages.g.o. |
6 |
|
7 |
Revision Changes Path |
8 |
1.10 xml/htdocs/proj/en/releng/docs/cascading-profiles.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/releng/docs/cascading-profiles.xml?rev=1.10&view=markup |
11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/releng/docs/cascading-profiles.xml?rev=1.10&content-type=text/plain |
12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/releng/docs/cascading-profiles.xml?r1=1.9&r2=1.10 |
13 |
|
14 |
Index: cascading-profiles.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/releng/docs/cascading-profiles.xml,v |
17 |
retrieving revision 1.9 |
18 |
retrieving revision 1.10 |
19 |
diff -u -r1.9 -r1.10 |
20 |
--- cascading-profiles.xml 13 Jul 2007 20:58:36 -0000 1.9 |
21 |
+++ cascading-profiles.xml 28 Nov 2007 20:22:39 -0000 1.10 |
22 |
@@ -1,5 +1,5 @@ |
23 |
<?xml version='1.0' encoding="UTF-8"?> |
24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/releng/docs/cascading-profiles.xml,v 1.9 2007/07/13 20:58:36 neysx Exp $ --> |
25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/releng/docs/cascading-profiles.xml,v 1.10 2007/11/28 20:22:39 robbat2 Exp $ --> |
26 |
<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?> |
27 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
28 |
|
29 |
@@ -85,14 +85,14 @@ |
30 |
the <path>use.defaults</path> file -- these USE flags are common to |
31 |
all the architectures thus far. Looking at the |
32 |
<path>packages</path> file, you might wonder where <uri |
33 |
- link="http://packages.gentoo.org/packages/?category=sys-apps;name=util-linux">util-linux</uri> |
34 |
+ link="http://packages.gentoo.org/package/sys-apps/util-linux">util-linux</uri> |
35 |
package went. Well, seeing as there are efforts to expand Gentoo into |
36 |
the worlds of <uri |
37 |
link="http://www.gnu.org/software/hurd/">GNU/Hurd</uri>, <uri |
38 |
link="http://www.openbsd.org/">OpenBSD</uri> and so on, the thinking |
39 |
was that the base profile should be applicable to those as well. |
40 |
Admittedly, <uri |
41 |
- link="http://packages.gentoo.org/packages/?category=sus-apps;name=coreutils">coreutils</uri> |
42 |
+ link="http://packages.gentoo.org/package/sus-apps/coreutils">coreutils</uri> |
43 |
seems a little GNU specific, but one step at a time.</p> |
44 |
<p>Hopefully, once you read the files in the base directory, you |
45 |
will agree that for the most part, it describes an implementation |
46 |
@@ -134,10 +134,10 @@ |
47 |
sub-architecture profiles. These profiles essentially delineate, |
48 |
again in fairly high-level terms, the differences between the |
49 |
sub-architectures. As an example, <uri |
50 |
- link="http://packages.gentoo.org/packages/?category=sys-devel;name=gcc-sparc64">gcc-sparc64</uri> is required on the |
51 |
+ link="http://packages.gentoo.org/package/sys-devel/gcc-sparc64">gcc-sparc64</uri> is required on the |
52 |
SPARC64 profiles, but <b>not</b> permitted on the SPARC32 profiles, |
53 |
yet they both use the same <uri |
54 |
- link="http://packages.gentoo.org/packages/?category=sys-boot;name=silo">bootloader</uri>. |
55 |
+ link="http://packages.gentoo.org/package/sys-boot/silo">bootloader</uri>. |
56 |
Thus, the bootloader would be in the parent (architecture specific) |
57 |
profile, and the gcc-sparc64 package would be defined in the |
58 |
sparc64 sub-architecture profile.</p> |
59 |
@@ -272,7 +272,7 @@ |
60 |
architecture class uses a different default bootlader from the |
61 |
others. Additionally, there may architecture specific things that |
62 |
are required as part of the base system, such as: <uri |
63 |
- link="http://packages.gentoo.org/packages/?category=sys-apps;name=sparc-utils">sparc-utils</uri> |
64 |
+ link="http://packages.gentoo.org/package/sys-apps/sparc-utils">sparc-utils</uri> |
65 |
for SPARC. Some architectures prefer to mask out the architecture |
66 |
USE flags for the other architectures. For example. the sparc |
67 |
profile puts <c>x86</c>, <c>ppc</c>, <c>alpha</c> and <c>mips</c> |
68 |
|
69 |
|
70 |
|
71 |
-- |
72 |
gentoo-commits@g.o mailing list |