Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-commits
Navigation:
Lists: gentoo-commits: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-commits@g.o
From: "Jeremy Olexa (darkside)" <darkside@g.o>
Subject: gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: ecopy.xml
Date: Sat, 01 Aug 2009 23:54:26 +0000
darkside    09/08/01 23:54:26

  Modified:             ecopy.xml
  Log:
  Update ecopy.xml with new output and some additional info

Revision  Changes    Path
1.4                  xml/htdocs/proj/en/gentoo-alt/prefix/ecopy.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/ecopy.xml?rev=1.4&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/ecopy.xml?rev=1.4&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/ecopy.xml?r1=1.3&r2=1.4

Index: ecopy.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/ecopy.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ecopy.xml	12 Nov 2008 23:51:32 -0000	1.3
+++ ecopy.xml	1 Aug 2009 23:54:26 -0000	1.4
@@ -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/ecopy.xml,v 1.3 2008/11/12 23:51:32 darkside Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/ecopy.xml,v 1.4 2009/08/01 23:54:26 darkside Exp $ -->
 
 <guide link="/proj/en/gentoo-alt/prefix/ecopy.xml" lang="en">
   <title>Importing ebuilds in Gentoo Prefix</title>
@@ -18,8 +18,8 @@
   <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
   <license/>
 
-  <version>1.1</version>
-  <date>2008-11-11</date>
+  <version>1.2</version>
+  <date>2009-08-01</date>
 
   <chapter>
     <title>Importing ebuilds with ecopy</title>
@@ -41,12 +41,11 @@
       <title>The ecopy script</title>
       <body>
         <p>
-          <c>ecopy</c>
-          is a script created by the Gentoo Prefix team, and located in
-          <c>${EPREFIX}/usr/portage/scripts</c>.  Its intention is to
-          save people time and is mainly a wrapper for other scripts
+          <c>ecopy</c> is a script created by the Gentoo Prefix team, and
+          located in <c>${EPREFIX}/usr/portage/scripts</c>.  Its intention is
+          to  save people time and is mainly a wrapper for other scripts
           which will be discussed later. Its usage can be described by
-          running: <c>ecopy</c>.
+          running: <c>ecopy</c> (without options).
         </p>
         <p><c>ecopy</c> expects the following:</p>
         <ul>
@@ -61,10 +60,6 @@
             <c>app-office/openoffice</c>.
           </li>
           <li>
-            Expects <c>${EPREFIX}/usr/portage/scripts</c> to be in your
-            path.
-          </li>
-          <li>
             Expects an up-to-date Prefix tree to reliably have the
             latest scripts.
           </li>
@@ -72,30 +67,44 @@
         <p>
           The use of <c>ecopy</c> is best explained by a simple example.
         </p>
-        <pre caption="ecopy example">% <i>export PATH="${PATH}:${EPREFIX}/usr/portage/scripts"</i>
+        <pre caption="ecopy example">
 % <i>cd "${EPREFIX}"/usr/local/portage/my-overlay</i>
 % <i>ecopy app-office/openoffice</i>
-openoffice-3.0.0_beta2.ebuild
-2008-09-03 08:36:39 URL:http://prefix.gentooexperimental.org/rsync-gentoo-x86/app-office/openoffice/ChangeLog [85281/85281] -> "ChangeLog" [1]
-2008-09-03 08:36:40 URL:http://prefix.gentooexperimental.org/rsync-gentoo-x86/app-office/openoffice/metadata.xml [635/635] -> "metadata.xml" [1]
-2008-09-03 08:36:40 URL:http://prefix.gentooexperimental.org/rsync-gentoo-x86/app-office/openoffice/Manifest [8510/8510] -> "Manifest" [1]
-2008-09-03 08:36:40 URL:http://prefix.gentooexperimental.org/rsync-gentoo-x86/app-office/openoffice/openoffice-3.0.0_beta2.ebuild [12662/12662] -> "openoffice-3.0.0_beta2.ebuild" [1]
-2008-09-03 08:36:41 URL:http://prefix.gentooexperimental.org/rsync-gentoo-x86/app-office/openoffice/files/gentoo-3.0.0_beta2.diff [1217/1217] -> "files/gentoo-3.0.0_beta2.diff" [1]
-2008-09-03 08:36:41 URL:http://prefix.gentooexperimental.org/rsync-gentoo-x86/app-office/openoffice/files/ooo-env_log.diff [617/617] -> "files/ooo-env_log.diff" [1]
-Processing openoffice-3.0.0_beta2.ebuild
-  EAPI ... added EAPI="prefix"
+openoffice-3.1.0-r1.ebuild
+2009-08-01 18:41:23 URL:http://tinderbox.dev.gentoo.org/portage/app-office/openo
+ffice/ChangeLog [98520/98520] -> "ChangeLog" [1]
+2009-08-01 18:41:23 URL:http://tinderbox.dev.gentoo.org/portage/app-office/openo
+ffice/metadata.xml [704/704] -> "metadata.xml" [1]
+2009-08-01 18:41:24 URL:http://tinderbox.dev.gentoo.org/portage/app-office/openo
+ffice/Manifest [17937/17937] -> "Manifest" [1]
+2009-08-01 18:41:24 URL:http://tinderbox.dev.gentoo.org/portage/app-office/openo
+ffice/openoffice-3.1.0-r1.ebuild [13564/13564] -> "openoffice-3.1.0-r1.ebuild" [
+1]
+2009-08-01 18:41:25 URL:http://tinderbox.dev.gentoo.org/portage/app-office/openo
+ffice/files/gentoo-3.1.0.diff [173/173] -> "files/gentoo-3.1.0.diff" [1]
+2009-08-01 18:41:25 URL:http://tinderbox.dev.gentoo.org/portage/app-office/openo
+ffice/files/ooo-env_log.diff [617/617] -> "files/ooo-env_log.diff" [1]
+2009-08-01 18:41:25 URL:http://tinderbox.dev.gentoo.org/portage/app-office/openo
+ffice/files/base64.diff [770/770] -> "files/base64.diff" [1]
+2009-08-01 18:41:25 URL:http://tinderbox.dev.gentoo.org/portage/app-office/openo
+ffice/files/buildfix-gcc44.diff [611/611] -> "files/buildfix-gcc44.diff" [1]
+2009-08-01 18:41:25 URL:http://tinderbox.dev.gentoo.org/portage/app-office/openo
+ffice/files/solenv.workaround-for-the-kde-mess.diff [17556/17556] -> "files/sole
+nv.workaround-for-the-kde-mess.diff" [1]
+2009-08-01 18:41:26 URL:http://tinderbox.dev.gentoo.org/portage/app-office/openo
+ffice/files/xulrunner-1.9.1.diff [325/325] -> "files/xulrunner-1.9.1.diff" [1]
+Processing openoffice-3.1.0-r1.ebuild
   replacing ${D} -> ${ED} ... 2 occurences
   replacing ${ROOT} -> ${EROOT} ... not found
-Processing openoffice-3.0.0_beta2.ebuild ... ~amd64-linux ~x86-linux
-openoffice-3.0.0_beta2.ebuild
+Processing openoffice-3.1.0-r1.ebuild ... ~amd64-linux ~x86-linux
+openoffice-3.1.0-r1.ebuild
 >>> Creating Manifest for usr/local/portage/my-overlay/app-office/openoffice
 &lt;snip for brevity&gt;</pre>
         <p>
           What is <c>ecopy</c> doing? In that above code snippet,
           <c>ecopy</c> first directly downloads the required files from
-          <c>gentooexperimental.org</c> (ge.o).  This is intended and an
-          appreciated service from the ge.o admins.  Then, <c>ecopy</c>
-          runs <c>eapify</c> on the ebuild.  <c>eapify</c> basically
+          <c>tinderbox.dev.gentoo.org</c>. Then, <c>ecopy</c>
+          runs <c>eapify</c> on the ebuild. <c>eapify</c> basically
           does the needed gentoo-x86 -&gt; Prefix conversion.  This can
           generally be automated and works right the first time about
           85% of the time.  After <c>eapify</c>, some keyword cleanup is
@@ -104,8 +113,9 @@
           the gentoo-x86 tree.  For more information on that see <uri
             link="http://www.gentoo.org/proj/en/glep/glep-0053.html">GLEP
             53</uri>. Last, <c>ecopy</c> re-digests the ebuild to
-          accomandate any changes.  Let it be known that you can do all
-          this manually as well.
+          accommodate any changes.  Let it be known that you can do all
+          this manually as well because <c>ecopy</c> is just a wrapper script in
+          itself.
         </p>
         <p>
           While <c>eapfiy</c> (the tool that does the actual
@@ -113,8 +123,8 @@
           cases, it cannot be trusted to always do the right thing.
           Common mistakes made by <c>eapify</c> are related to either
           adding or omission of the <c>${EPREFIX}</c> for some component
-          in the ebuild.  <c>eapify</c> doesn't catch all instances of
-          what needs to be changed.  If there is e.g. any path hardcoded
+          in the ebuild. <c>eapify</c> doesn't catch all instances of
+          what needs to be changed. If there is e.g. any path hardcoded
           in the configure call you will need to prepend
           <c>${EPREFIX}</c> to it.  Also, <c>${D}</c> can be improperly
           expanded to <c>${ED}</c> in certain cases.  Manual review is
@@ -134,7 +144,7 @@
       <p>
       Great, your package works...now what? The Gentoo Prefix team relies on
       users submitting bug reports stating if a new package works. We simply do
-      not have the man power to get to our goal of having most of the packages 
+      not have the man power to get to our goal of having most of the packages
       in the Prefix tree without your help.
       </p>
       <p>
@@ -157,7 +167,13 @@
         bundled with anything else.
         </li>
         <li>
-        Include emerge --info
+        Include emerge --info, or at least what ARCH you are on. Otherwise, we
+        will commit the package and have to re-visit it to add your arch.
+        </li>
+        <li>
+        Do not submit reports about <c>ecopy</c> not porting your package
+        correctly, it is a best effort script only! Manual work probably is
+        needed.
         </li>
       </ul>
       </body>





Navigation:
Lists: gentoo-commits: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: ecopy.xml
Next by thread:
gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: ecopy.xml
Previous by date:
gentoo commit in xml/htdocs/doc/en: fluxbox-config.xml
Next by date:
gentoo-x86 commit in games-engines/scummvm: ChangeLog scummvm-0.13.1.ebuild


Updated Jun 26, 2012

Summary: Archive of the gentoo-commits mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.