* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: techdocs.xml
@ 2007-09-23 13:26 Fabian Groffen (grobian)
0 siblings, 0 replies; 10+ messages in thread
From: Fabian Groffen (grobian) @ 2007-09-23 13:26 UTC (permalink / raw
To: gentoo-commits
grobian 07/09/23 13:26:54
Modified: techdocs.xml
Log:
Adding some policies on making changes to the ebuilds.
Revision Changes Path
1.9 xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.9&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.9&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?r1=1.8&r2=1.9
Index: techdocs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- techdocs.xml 11 Aug 2007 18:44:04 -0000 1.8
+++ techdocs.xml 23 Sep 2007 13:26:54 -0000 1.9
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.8 2007/08/11 18:44:04 grobian Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.9 2007/09/23 13:26:54 grobian Exp $ -->
<guide link="/proj/en/gentoo-alt/prefix/techdocs.xml" lang="en">
<title>Gentoo Prefixed Portage Techdocs</title>
@@ -270,6 +270,85 @@
connection between the Prefix tree and the main tree.
</p>
</body>
+ </section><!-- }}} -->
+
+ </chapter>
+
+ <chapter>
+ <title>Prefix tree developer policies</title>
+
+ <section><!-- {{{ updating -->
+ <title>Main tree migrations</title>
+ <body>
+ <p>
+ In principle, all ebuilds in the Prefix tree are modified
+ copies from their versions in the main tree, as used by Gentoo
+ Linux. This means that each ebuild is copied and hence needs
+ to be kept in sync with the main tree version. Since ebuilds
+ in the Prefix tree may have manual modifications (those not
+ automatically made by <c>eapify</c>), the process of keeping
+ the Prefix tree in sync with the main tree is not as straight
+ forward as simply re-copying and re-<c>eapify</c>ing.
+ Instead, a complex script, <c>eupdate</c> is used to apply the
+ differences made to an ebuild in the main tree, to the version
+ in the Prefix tree. Also when new versions of ebuilds are
+ added to the main tree, the <c>eupdate</c> script derives a
+ new version in the Prefix tree, based on the differences
+ between the latest two versions of the ebuilds in the main
+ tree. This process is called a <e>cross-diff</e>. Both
+ updating strategies may fail depending on modifications made
+ to the ebuild in the Prefix tree. In 90% of the cases, both
+ update strategies apply without problems, and semi-automatic
+ propagation relies on that to currently merge changes from the
+ main tree on a daily basis, with a limited investment of time
+ on (manually) resolving the conflicts.
+ </p>
+ <p>
+ Mainly because manually resolving conflicts is a tedious job,
+ the main policy in the Prefix tree with regard to
+ modifications made to the main tree version is sound and
+ simple: <b>avoid any change that is not strictly
+ necessary</b>!. This boils down to the following concrete
+ rules that need to be taken into account. Quoting of
+ variables is a often confusing job. Underquoting results in
+ problems when spaces are being used, overquoting is just
+ unnecessary work. In many cases, the quoting of variables is
+ done wrong in the main tree ebuilds, hence the problem is also
+ carried over onto the Prefix tree. Fixing these quoting
+ problems should <e>not</e> be done, unless this is necessary
+ to solve a Prefix specific problem, which happens only in rare
+ cases. Along the same line, adding or removing white space,
+ indenting, rewriting to make more optimal in execution and
+ similar changes which are not essentially necessary, should be
+ avoided. To avoid differences in the <c>Changelog</c> file,
+ you should <e>not</e> use <c>echangelog</c> when committing
+ changes to ebuilds that are available in the main tree, and
+ hence subject to semi-automatic updating. In fact each
+ <c>Changelog</c> entry added using <c>echangelog</c> makes a
+ conflict during updating, making the problem even worse.
+ Don't update the <c>ChangeLog</c>.
+ </p>
+ <p>
+ When changes need to be made, such as adding an <c>epatch</c>
+ line, or adding a platform specific statement, such as an
+ configure option, care needs to be taken to try to reduce the
+ size of the differences introduced. The smaller the
+ difference, the bigger the chance that semi-automatic updating
+ succeeds without problems.
+ </p>
+ <p>
+ For files that have no CVS header, and hence cannot be kept in
+ sync, such as e.g. <c>metadata.xml</c> and many patches in the
+ <c>files/</c> directory the <c>eupdate</c> command just makes
+ sure it is equal to the version in the main tree. For this
+ reason, keep in mind that changes to those files get lost upon
+ the next run of <c>eupdate</c>. Since this is done almost
+ daily, the modifications disappear soon enough. Only files
+ with a CVS <c>$ Header</c><c>:</c> <!-- no-expansion hack ;) -->
+ (such as ebuilds) can be changed in such a way that the
+ modifications are not lost.
+ </p>
+ </body>
</section>
</chapter>
--
gentoo-commits@gentoo.org mailing list
^ permalink raw reply [flat|nested] 10+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: techdocs.xml
@ 2008-10-31 14:49 Jeremy Olexa (darkside)
0 siblings, 0 replies; 10+ messages in thread
From: Jeremy Olexa (darkside) @ 2008-10-31 14:49 UTC (permalink / raw
To: gentoo-commits
darkside 08/10/31 14:49:30
Modified: techdocs.xml
Log:
fix typo, missing '}'
Revision Changes Path
1.11 xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.11&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.11&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?r1=1.10&r2=1.11
Index: techdocs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- techdocs.xml 18 Mar 2008 21:49:51 -0000 1.10
+++ techdocs.xml 31 Oct 2008 14:49:30 -0000 1.11
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.10 2008/03/18 21:49:51 grobian Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.11 2008/10/31 14:49:30 darkside Exp $ -->
<guide link="/proj/en/gentoo-alt/prefix/techdocs.xml" lang="en">
<title>Gentoo Prefix Techdocs</title>
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
- <version>1.2</version>
- <date>2008-03-18</date>
+ <version>1.21</version>
+ <date>2008-10-31</date>
<chapter>
<title>Changes to Portage</title>
@@ -219,7 +219,7 @@
</p>
<p>
This rule basically means that you <e>never</e> add
- <c>${EROOT</c> yourself, if there isn't a <c>${ROOT}</c> in
+ <c>${EROOT}</c> yourself, if there isn't a <c>${ROOT}</c> in
the main tree ebuild. Repeating: whether or not that is
"correct", for Gentoo Prefix this rule always holds. Rationale is
simple: if it is a bug, it is a bug that should be fixed
^ permalink raw reply [flat|nested] 10+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: techdocs.xml
@ 2009-03-23 19:58 Fabian Groffen (grobian)
0 siblings, 0 replies; 10+ messages in thread
From: Fabian Groffen (grobian) @ 2009-03-23 19:58 UTC (permalink / raw
To: gentoo-commits
grobian 09/03/23 19:58:26
Modified: techdocs.xml
Log:
make note about eprefix.eclass and its most important function eprefixify
Revision Changes Path
1.12 xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.12&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.12&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?r1=1.11&r2=1.12
Index: techdocs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- techdocs.xml 31 Oct 2008 14:49:30 -0000 1.11
+++ techdocs.xml 23 Mar 2009 19:58:26 -0000 1.12
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.11 2008/10/31 14:49:30 darkside Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.12 2009/03/23 19:58:26 grobian Exp $ -->
<guide link="/proj/en/gentoo-alt/prefix/techdocs.xml" lang="en">
<title>Gentoo Prefix Techdocs</title>
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
- <version>1.21</version>
- <date>2008-10-31</date>
+ <version>1.22</version>
+ <date>2009-03-23</date>
<chapter>
<title>Changes to Portage</title>
@@ -275,6 +275,20 @@
</body>
</section><!-- }}} -->
+ <section><!-- {{{ prefix.eclass -->
+ <title>prefix.eclass</title>
+ <body>
+ <p>
+ In some cases, the offset prefix needs to be hardcoded into
+ files. Examples are shebangs with arguments or references to
+ config files. The <c>prefix.eclass</c> provides the function
+ <c>eprefixify</c>, which replaces each occurrence of
+ <c>@GENTOO_PORTAGE_EPREFIX@</c> with the offset prefix as
+ known by Portage. To use the eprefixify function on files
+ (e.g. after patching), one needs to inherit the prefix eclass.
+ </p>
+ </body>
+ </section><!-- }}} -->
</chapter>
<chapter>
^ permalink raw reply [flat|nested] 10+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: techdocs.xml
@ 2009-05-20 20:48 Jeremy Olexa (darkside)
0 siblings, 0 replies; 10+ messages in thread
From: Jeremy Olexa (darkside) @ 2009-05-20 20:48 UTC (permalink / raw
To: gentoo-commits
darkside 09/05/20 20:48:51
Modified: techdocs.xml
Log:
Remove EAPI=prefix part, that is no longer true
Revision Changes Path
1.13 xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.13&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.13&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?r1=1.12&r2=1.13
Index: techdocs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- techdocs.xml 23 Mar 2009 19:58:26 -0000 1.12
+++ techdocs.xml 20 May 2009 20:48:50 -0000 1.13
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.12 2009/03/23 19:58:26 grobian Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.13 2009/05/20 20:48:50 darkside Exp $ -->
<guide link="/proj/en/gentoo-alt/prefix/techdocs.xml" lang="en">
<title>Gentoo Prefix Techdocs</title>
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
- <version>1.22</version>
- <date>2009-03-23</date>
+ <version>1.23</version>
+ <date>2009-05-20</date>
<chapter>
<title>Changes to Portage</title>
@@ -131,23 +131,6 @@
<chapter>
<title>Ebuild modifications</title>
- <section><!-- {{{ EAPI -->
- <title>Introduction of EAPI</title>
- <body>
- <p>
- The variable <c>EAPI</c> is currently slowly making its way
- into main tree ebuilds. <c>EAPI</c> identifies the API
- Portage has to
- support in order to process an ebuild. The <c>EAPI</c> chosen
- to indicate an ebuild is ported to Prefix, is "prefix".
- Hence, each ebuild that wants to be used with Gentoo Prefix
- has to declare <c>EAPI="prefix"</c>. Typically, this
- declaration is done first thing in the ebuild after the (CVS)
- header.
- </p>
- </body>
- </section><!-- }}} -->
-
<section><!-- {{{ EPREFIX -->
<title>EPREFIX variable</title>
<body>
^ permalink raw reply [flat|nested] 10+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: techdocs.xml
@ 2011-01-28 15:41 Jeremy Olexa (darkside)
0 siblings, 0 replies; 10+ messages in thread
From: Jeremy Olexa (darkside) @ 2011-01-28 15:41 UTC (permalink / raw
To: gentoo-commits
darkside 11/01/28 15:41:31
Modified: techdocs.xml
Log:
Add note about inter-revisions in overlay only
Revision Changes Path
1.14 xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.14&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.14&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?r1=1.13&r2=1.14
Index: techdocs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- techdocs.xml 20 May 2009 20:48:50 -0000 1.13
+++ techdocs.xml 28 Jan 2011 15:41:30 -0000 1.14
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.13 2009/05/20 20:48:50 darkside Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.14 2011/01/28 15:41:30 darkside Exp $ -->
<guide link="/proj/en/gentoo-alt/prefix/techdocs.xml" lang="en">
<title>Gentoo Prefix Techdocs</title>
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
- <version>1.23</version>
- <date>2009-05-20</date>
+ <version>1.24</version>
+ <date>2011-01-28</date>
<chapter>
<title>Changes to Portage</title>
@@ -217,6 +217,8 @@
<section><!-- {{{ inter-revisions -->
<title>Ebuild inter-revisions</title>
<body>
+ <note>This subsection <b>only</b> applies to the Prefix Overlay, not
+ the main Gentoo Linux tree. </note>
<p>
Gentoo Prefix ebuilds are currently merged from the main tree,
and kept in sync. This process is half automated using
^ permalink raw reply [flat|nested] 10+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: techdocs.xml
@ 2011-02-04 18:53 Jeremy Olexa (darkside)
0 siblings, 0 replies; 10+ messages in thread
From: Jeremy Olexa (darkside) @ 2011-02-04 18:53 UTC (permalink / raw
To: gentoo-commits
darkside 11/02/04 18:53:35
Modified: techdocs.xml
Log:
move inter-revisions section down
Revision Changes Path
1.15 xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.15&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.15&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?r1=1.14&r2=1.15
Index: techdocs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- techdocs.xml 28 Jan 2011 15:41:30 -0000 1.14
+++ techdocs.xml 4 Feb 2011 18:53:35 -0000 1.15
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.14 2011/01/28 15:41:30 darkside Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.15 2011/02/04 18:53:35 darkside Exp $ -->
<guide link="/proj/en/gentoo-alt/prefix/techdocs.xml" lang="en">
<title>Gentoo Prefix Techdocs</title>
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
- <version>1.24</version>
- <date>2011-01-28</date>
+ <version>1.25</version>
+ <date>2011-02-04</date>
<chapter>
<title>Changes to Portage</title>
@@ -214,6 +214,21 @@
</body>
</section><!-- }}} -->
+ <section><!-- {{{ prefix.eclass -->
+ <title>prefix.eclass</title>
+ <body>
+ <p>
+ In some cases, the offset prefix needs to be hardcoded into
+ files. Examples are shebangs with arguments or references to
+ config files. The <c>prefix.eclass</c> provides the function
+ <c>eprefixify</c>, which replaces each occurrence of
+ <c>@GENTOO_PORTAGE_EPREFIX@</c> with the offset prefix as
+ known by Portage. To use the eprefixify function on files
+ (e.g. after patching), one needs to inherit the prefix eclass.
+ </p>
+ </body>
+ </section><!-- }}} -->
+
<section><!-- {{{ inter-revisions -->
<title>Ebuild inter-revisions</title>
<body>
@@ -259,21 +274,6 @@
</p>
</body>
</section><!-- }}} -->
-
- <section><!-- {{{ prefix.eclass -->
- <title>prefix.eclass</title>
- <body>
- <p>
- In some cases, the offset prefix needs to be hardcoded into
- files. Examples are shebangs with arguments or references to
- config files. The <c>prefix.eclass</c> provides the function
- <c>eprefixify</c>, which replaces each occurrence of
- <c>@GENTOO_PORTAGE_EPREFIX@</c> with the offset prefix as
- known by Portage. To use the eprefixify function on files
- (e.g. after patching), one needs to inherit the prefix eclass.
- </p>
- </body>
- </section><!-- }}} -->
</chapter>
<chapter>
^ permalink raw reply [flat|nested] 10+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: techdocs.xml
@ 2012-03-24 18:58 Fabian Groffen (grobian)
0 siblings, 0 replies; 10+ messages in thread
From: Fabian Groffen (grobian) @ 2012-03-24 18:58 UTC (permalink / raw
To: gentoo-commits
grobian 12/03/24 18:58:04
Modified: techdocs.xml
Log:
update link to portage sources, as pointed out by slyfox
Revision Changes Path
1.16 xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.16&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.16&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?r1=1.15&r2=1.16
Index: techdocs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- techdocs.xml 4 Feb 2011 18:53:35 -0000 1.15
+++ techdocs.xml 24 Mar 2012 18:58:04 -0000 1.16
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.15 2011/02/04 18:53:35 darkside Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.16 2012/03/24 18:58:04 grobian Exp $ -->
<guide link="/proj/en/gentoo-alt/prefix/techdocs.xml" lang="en">
<title>Gentoo Prefix Techdocs</title>
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
- <version>1.25</version>
- <date>2011-02-04</date>
+ <version>1.26</version>
+ <date>2012-03-24</date>
<chapter>
<title>Changes to Portage</title>
@@ -77,7 +77,7 @@
<path>prefix</path> branch of
the main Portage Subversion repository. Its sources can be
inspected at
- <uri>http://sources.gentoo.org/viewcvs.py/portage/main/branches/prefix/</uri>.
+ <uri>http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=shortlog;h=refs/heads/prefix</uri>.
<br />
Currently, the Portage in this branch code is very close to
the <c>trunk</c> in subversion. Patches made in the
^ permalink raw reply [flat|nested] 10+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: techdocs.xml
@ 2012-12-05 13:27 Fabian Groffen (grobian)
0 siblings, 0 replies; 10+ messages in thread
From: Fabian Groffen (grobian) @ 2012-12-05 13:27 UTC (permalink / raw
To: gentoo-commits
grobian 12/12/05 13:27:43
Modified: techdocs.xml
Log:
update techdocs, drop eapify reference
Revision Changes Path
1.18 xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.18&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.18&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?r1=1.17&r2=1.18
Index: techdocs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- techdocs.xml 28 Oct 2012 15:21:06 -0000 1.17
+++ techdocs.xml 5 Dec 2012 13:27:43 -0000 1.18
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.17 2012/10/28 15:21:06 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.18 2012/12/05 13:27:43 grobian Exp $ -->
<guide lang="en">
<title>Gentoo Prefix Techdocs</title>
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
- <version>1.26</version>
- <date>2012-03-24</date>
+ <version>1.27</version>
+ <date>2012-12-05</date>
<chapter>
<title>Changes to Portage</title>
@@ -94,33 +94,22 @@
<body>
<p>
- Since the Gentoo Linux Portage tree is not compatible with
- Gentoo Prefix, an overlay has been created, which is
+ Since the Gentoo Linux Portage tree is not always compatible
+ with Gentoo Prefix, an overlay has been created, which is
currently hosted on
<uri>http://overlays.gentoo.org/proj/alt/browser/trunk/prefix-overlay</uri>.
- This has the disadvantage of not inheriting all packages from
+ This has the disadvantage of not inheriting all changes and
+ fixes from
the main tree automatically. Instead each package has to be
- converted to be Prefix compatible. Luckily for most packages
- these changes are trivial, and can be automatically performed
- by the <c>eapify</c> script, which can be found in the
- <path>scripts</path> directory of the prefix-overlay.
+ converted to be Prefix compatible.
</p>
<p>
- Compared to the main tree, the Prefix tree is rather small.
- Adding packages is usually a simple job, using the tools from
- the <path>scripts</path> directory mentioned before. Keeping
- the packages synchronised with the main tree is also
+ Keeping the copied packages synchronised with the main tree is
facilitated by a script that is capable of applying the diffs
with some intelligence between revisions. Also "cross-diffs",
diffs between versions to create a new ebuild version,
retaining as much changes as added in the previous version are
implemented, keeping the maintenance overhead rather low.
- <br />
- While the Prefix tree contains enough packages to bootstrap a
- Prefix system, run some editor and read mail via <c>mutt</c>, it
- currently lacks packages in a number of areas. We are
- constantly looking on how to expand on these areas, but mostly
- rely on contributors doing the initial pioneer work.
</p>
</body>
@@ -143,8 +132,8 @@
<c>econf</c> at all. For those occasions the variable
<c>${EPREFIX}</c> is available in ebuilds and eclasses,
pointing to the root of the offset. For an offset
- <path>/Library/Gentoo</path> for example, the variable
- <c>${EPREFIX}</c> would contain <path>/Library/Gentoo</path>.
+ <path>/home/user/gentoo</path> for example, the variable
+ <c>${EPREFIX}</c> would contain <path>/home/user/gentoo</path>.
This allows to easily use it for example like <c>econf
--with-some-app="${EPREFIX}"/usr/bin/some-app</c>.
</p>
@@ -202,7 +191,7 @@
</p>
<p>
This rule basically means that you <e>never</e> add
- <c>${EROOT}</c> yourself, if there isn't a <c>${ROOT}</c> in
+ <c>${EROOT}</c> yourself, if there isn't a <c>${ROOT}</c> in
the main tree ebuild. Repeating: whether or not that is
"correct", for Gentoo Prefix this rule always holds. Rationale is
simple: if it is a bug, it is a bug that should be fixed
@@ -232,13 +221,14 @@
<section><!-- {{{ inter-revisions -->
<title>Ebuild inter-revisions</title>
<body>
- <note>This subsection <b>only</b> applies to the Prefix Overlay, not
- the main Gentoo Linux tree. </note>
+ <note>This subsection <b>only</b> applies to the Prefix Overlay, not
+ the main Gentoo Linux tree, and the use of inter-revisions is
+ highly discouraged!</note>
<p>
Gentoo Prefix ebuilds are currently merged from the main tree,
and kept in sync. This process is half automated using
scripts and in short takes differences from the main tree to
- apply them on the Prefix tree. This process assures that
+ apply them on the Prefix tree. This process insures that
changes made to the Prefix tree are not lost, where it still
is possible to merge most changes. For this to work, the
ebuilds need to keep the same filename as in the main tree
@@ -287,10 +277,10 @@
copies from their versions in the main tree, as used by Gentoo
Linux. This means that each ebuild is copied and hence needs
to be kept in sync with the main tree version. Since ebuilds
- in the Prefix tree may have manual modifications (those not
- automatically made by <c>eapify</c>), the process of keeping
+ in the Prefix tree all have manual modifications (those not
+ automatically scriptable), the process of keeping
the Prefix tree in sync with the main tree is not as straight
- forward as simply re-copying and re-<c>eapify</c>ing.
+ forward as simply running a script.
Instead, a complex script, <c>eupdate</c> is used to apply the
differences made to an ebuild in the main tree, to the version
in the Prefix tree. Also when new versions of ebuilds are
@@ -350,6 +340,18 @@
(such as ebuilds) can be changed in such a way that the
modifications are not lost.
</p>
+ <p>
+ The good news is that Gentoo Prefix lives for a great deal in
+ gx86, these days. Thus, the prefix overlay is being emptied,
+ by migrating its packages to gx86. This requires contacting
+ the gx86 maintainers and getting them to accept the changes
+ necessary. Often, ebuilds in the prefix overlay need cleaning
+ up, and reevaluation if hacks, patches and other changes are
+ still necessary. Remember that many ebuilds have grown over
+ years in the prefix overlay, and hence not necessarily are the
+ cleanest solution. We aim not to add anything to our overlay
+ any more, and move more and more towards acceptance in gx86.
+ </p>
</body>
</section>
^ permalink raw reply [flat|nested] 10+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: techdocs.xml
@ 2013-11-11 20:59 Fabian Groffen (grobian)
0 siblings, 0 replies; 10+ messages in thread
From: Fabian Groffen (grobian) @ 2013-11-11 20:59 UTC (permalink / raw
To: gentoo-commits
grobian 13/11/11 20:59:35
Modified: techdocs.xml
Log:
techdocs: update to reality, fix defs, bug #490920
Revision Changes Path
1.19 xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.19&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.19&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?r1=1.18&r2=1.19
Index: techdocs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- techdocs.xml 5 Dec 2012 13:27:43 -0000 1.18
+++ techdocs.xml 11 Nov 2013 20:59:35 -0000 1.19
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.18 2012/12/05 13:27:43 grobian Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.19 2013/11/11 20:59:35 grobian Exp $ -->
<guide lang="en">
<title>Gentoo Prefix Techdocs</title>
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
- <version>1.27</version>
- <date>2012-12-05</date>
+ <version>1.28</version>
+ <date>2013-11-11</date>
<chapter>
<title>Changes to Portage</title>
@@ -63,6 +63,10 @@
portage development: Prefix. In this branch, initially
managed by Brian Harring, then later by Kito Dietrich, lots of
development made Prefix portage into what it is currently.
+ Fabian Groffen did lots of work on getting the Portage sources
+ usable for everyday Prefix use. Currently, the Prefix branch
+ of the Portage tree benefits a lot from the efforts of Zac
+ Medico to make Prefix a first class feature of Portage.
</p>
</body>
@@ -80,8 +84,8 @@
<uri>http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=shortlog;h=refs/heads/prefix</uri>.
<br />
Currently, the Portage in this branch code is very close to
- the <c>trunk</c> in subversion. Patches made in the
- <c>trunk</c> usually apply cleanly to the <c>prefix</c>
+ the <c>master</c> branch in git. Patches made in
+ <c>master</c> usually apply cleanly to the <c>prefix</c>
branch. Hence, it is easy to keep the two synchronised using
frequent merge operations.
</p>
@@ -98,13 +102,13 @@
with Gentoo Prefix, an overlay has been created, which is
currently hosted on
<uri>http://overlays.gentoo.org/proj/alt/browser/trunk/prefix-overlay</uri>.
- This has the disadvantage of not inheriting all changes and
- fixes from
- the main tree automatically. Instead each package has to be
- converted to be Prefix compatible.
+ This overlay is really overlaid on the main Gentoo Portage
+ tree, and provided as such to Prefix users from the Prefix
+ rsync mirror.
</p>
<p>
- Keeping the copied packages synchronised with the main tree is
+ Keeping the copied packages in the overlay synchronised with
+ the main tree is
facilitated by a script that is capable of applying the diffs
with some intelligence between revisions. Also "cross-diffs",
diffs between versions to create a new ebuild version,
@@ -150,11 +154,11 @@
Prefix <c>configure</c> is run with <c>--prefix=${EPREFIX}/usr</c>
in principle no changes are required. However,
for all modifications to the build image, as is common
- practise in many ebuilds, <c>${D}${EPREFIX}</c> should be
+ practise in many ebuilds, <c>${D%/}${EPREFIX}</c> should be
used. While this is a clean and logical result of using an
offset, it increases the burden of "porting" ebuilds. For
this purpose the variable <c>${ED}</c> was introduced. It
- contains the value of <c>${D}${EPREFIX}/</c> and functions as
+ contains the value of <c>${D%/}${EPREFIX}/</c> and functions as
handy shortcut, which is easy to change. Usually, all but one
occurrences of <c>${D}</c> in an ebuild (or eclass) have to be
replaced by <c>${ED}</c> to work properly in the prefix.
@@ -165,7 +169,7 @@
<p>
The variable <c>${ROOT}</c> has for the same purpose a
corresponding <c>${EROOT}</c> which contains
- <c>${ROOT}${EPREFIX}</c>. Often when <c>${ROOT}</c> is being
+ <c>${ROOT%/}${EPREFIX}/</c>. Often when <c>${ROOT}</c> is being
used, this can be replaced by <c>${EROOT}</c> to add Gentoo
Prefix support.
</p>
^ permalink raw reply [flat|nested] 10+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: techdocs.xml
@ 2015-02-19 22:17 Andreas HAttel (dilfridge)
0 siblings, 0 replies; 10+ messages in thread
From: Andreas HAttel (dilfridge) @ 2015-02-19 22:17 UTC (permalink / raw
To: gentoo-commits
dilfridge 15/02/19 22:17:23
Modified: techdocs.xml
Log:
Migrate to wiki
Revision Changes Path
1.23 xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.23&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?rev=1.23&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml?r1=1.22&r2=1.23
Index: techdocs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- techdocs.xml 24 Jan 2014 20:36:31 -0000 1.22
+++ techdocs.xml 19 Feb 2015 22:17:23 -0000 1.23
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.22 2014/01/24 20:36:31 grobian Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/techdocs.xml,v 1.23 2015/02/19 22:17:23 dilfridge Exp $ -->
-<guide lang="en">
+<guide lang="en" disclaimer="obsolete" redirect="http://wiki.gentoo.org/wiki/Project:Prefix/Technical_Documentation">
<title>Gentoo Prefix Techdocs</title>
<author title="Author">
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2015-02-19 22:17 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-10-31 14:49 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: techdocs.xml Jeremy Olexa (darkside)
-- strict thread matches above, loose matches on Subject: below --
2015-02-19 22:17 Andreas HAttel (dilfridge)
2013-11-11 20:59 Fabian Groffen (grobian)
2012-12-05 13:27 Fabian Groffen (grobian)
2012-03-24 18:58 Fabian Groffen (grobian)
2011-02-04 18:53 Jeremy Olexa (darkside)
2011-01-28 15:41 Jeremy Olexa (darkside)
2009-05-20 20:48 Jeremy Olexa (darkside)
2009-03-23 19:58 Fabian Groffen (grobian)
2007-09-23 13:26 Fabian Groffen (grobian)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox