| 1 |
tommy 09/03/23 18:41:17 |
| 2 |
|
| 3 |
Modified: skel.ebuild |
| 4 |
Log: |
| 5 |
Update skel.ebuild as announced at gentoo-dev ML |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.52 skel.ebuild |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/skel.ebuild?rev=1.52&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/skel.ebuild?rev=1.52&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/skel.ebuild?r1=1.51&r2=1.52 |
| 13 |
|
| 14 |
Index: skel.ebuild |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo-x86/skel.ebuild,v |
| 17 |
retrieving revision 1.51 |
| 18 |
retrieving revision 1.52 |
| 19 |
diff -u -r1.51 -r1.52 |
| 20 |
--- skel.ebuild 1 Jan 2009 01:21:22 -0000 1.51 |
| 21 |
+++ skel.ebuild 23 Mar 2009 18:41:17 -0000 1.52 |
| 22 |
@@ -21,14 +21,14 @@ |
| 23 |
|
| 24 |
# inherit lists eclasses to inherit functions from. Almost all ebuilds should |
| 25 |
# inherit eutils, as a large amount of important functionality has been |
| 26 |
-# moved there. For example, the $(get_libdir) mentioned below wont work |
| 27 |
+# moved there. For example, the epatch call mentioned below wont work |
| 28 |
# without the following line: |
| 29 |
inherit eutils |
| 30 |
# A well-used example of an eclass function that needs eutils is epatch. If |
| 31 |
# your source needs patches applied, it's suggested to put your patch in the |
| 32 |
# 'files' directory and use: |
| 33 |
# |
| 34 |
-# epatch ${FILESDIR}/patch-name-here |
| 35 |
+# epatch "${FILESDIR}"/patch-name-here |
| 36 |
# |
| 37 |
# eclasses tend to list descriptions of how to use their functions properly. |
| 38 |
# take a look at /usr/portage/eclasses/ for more examples. |
| 39 |
@@ -96,7 +96,7 @@ |
| 40 |
# had installed on your system when you tested the package. Then |
| 41 |
# other users hopefully won't be caught without the right version of |
| 42 |
# a dependency. |
| 43 |
-DEPEND="" |
| 44 |
+#DEPEND="" |
| 45 |
|
| 46 |
# Run-time dependencies. Must be defined to whatever this depends on to run. |
| 47 |
# The below is valid if the same run-time depends are required to compile. |
| 48 |
@@ -108,10 +108,13 @@ |
| 49 |
# to keep it tidy. |
| 50 |
#S="${WORKDIR}/${P}" |
| 51 |
|
| 52 |
-src_compile() { |
| 53 |
+ |
| 54 |
+# The following src_compile function is implemented as default by portage, so |
| 55 |
+# you only need to call it, if you need a different behaviour. |
| 56 |
+#src_compile() { |
| 57 |
# Most open-source packages use GNU autoconf for configuration. |
| 58 |
- # The quickest (and preferred) way of running configure is: |
| 59 |
- econf || die "econf failed" |
| 60 |
+ # The default, quickest (and preferred) way of running configure is: |
| 61 |
+ #econf |
| 62 |
# |
| 63 |
# You could use something similar to the following lines to |
| 64 |
# configure your package before compilation. The "|| die" portion |
| 65 |
@@ -135,8 +138,9 @@ |
| 66 |
# related to parallelism, in these cases, use emake -j1 to limit |
| 67 |
# make to a single process. The -j1 is a visual clue to others |
| 68 |
# that the makefiles have bugs that have been worked around. |
| 69 |
- emake || die "emake failed" |
| 70 |
-} |
| 71 |
+ |
| 72 |
+ #emake || die "emake failed" |
| 73 |
+#} |
| 74 |
|
| 75 |
src_install() { |
| 76 |
# You must *personally verify* that this trick doesn't install |
Archives