| 1 | # Copyright 1999-2008 Gentoo Foundation |
1 | # Copyright 1999-2009 Gentoo Foundation |
| 2 | # Distributed under the terms of the GNU General Public License v2 |
2 | # Distributed under the terms of the GNU General Public License v2 |
| 3 | # $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.48 2008/03/13 23:05:53 spb Exp $ |
3 | # $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.52 2009/03/23 18:41:17 tommy Exp $ |
| 4 | |
4 | |
| 5 | # NOTE: The comments in this file are for instruction and documentation. |
5 | # NOTE: The comments in this file are for instruction and documentation. |
| 6 | # They're not meant to appear with your final, production ebuild. Please |
6 | # They're not meant to appear with your final, production ebuild. Please |
| 7 | # remember to remove them before submitting or committing your ebuild. That |
7 | # remember to remove them before submitting or committing your ebuild. That |
| 8 | # doesn't mean you can't add your own comments though. |
8 | # doesn't mean you can't add your own comments though. |
| … | |
… | |
| 10 | # The 'Header' on the third line should just be left alone. When your ebuild |
10 | # The 'Header' on the third line should just be left alone. When your ebuild |
| 11 | # will be committed to cvs, the details on that line will be automatically |
11 | # will be committed to cvs, the details on that line will be automatically |
| 12 | # generated to contain the correct data. |
12 | # generated to contain the correct data. |
| 13 | |
13 | |
| 14 | # The EAPI variable tells the ebuild format in use. |
14 | # The EAPI variable tells the ebuild format in use. |
| 15 | # Defaults to 0 if not specified. See current PMS draft for more details. |
15 | # Defaults to 0 if not specified. The current PMS draft contains details on |
|
|
16 | # a proposed EAPI=0 definition but is not finalized yet. |
| 16 | # Eclasses will test for this variable if they need to use EAPI > 0 features. |
17 | # Eclasses will test for this variable if they need to use EAPI > 0 features. |
| 17 | # Ebuilds should not define EAPI=1 unless they need to use features added |
18 | # Ebuilds should not define EAPI > 0 unless they absolutely need to use |
| 18 | # in that version. |
19 | # features added in that version. |
| 19 | #EAPI=1 |
20 | #EAPI=0 |
| 20 | |
21 | |
| 21 | # inherit lists eclasses to inherit functions from. Almost all ebuilds should |
22 | # inherit lists eclasses to inherit functions from. Almost all ebuilds should |
| 22 | # inherit eutils, as a large amount of important functionality has been |
23 | # inherit eutils, as a large amount of important functionality has been |
| 23 | # moved there. For example, the $(get_libdir) mentioned below wont work |
24 | # moved there. For example, the epatch call mentioned below wont work |
| 24 | # without the following line: |
25 | # without the following line: |
| 25 | inherit eutils |
26 | inherit eutils |
| 26 | # A well-used example of an eclass function that needs eutils is epatch. If |
27 | # A well-used example of an eclass function that needs eutils is epatch. If |
| 27 | # your source needs patches applied, it's suggested to put your patch in the |
28 | # your source needs patches applied, it's suggested to put your patch in the |
| 28 | # 'files' directory and use: |
29 | # 'files' directory and use: |
| 29 | # |
30 | # |
| 30 | # epatch ${FILESDIR}/patch-name-here |
31 | # epatch "${FILESDIR}"/patch-name-here |
| 31 | # |
32 | # |
| 32 | # eclasses tend to list descriptions of how to use their functions properly. |
33 | # eclasses tend to list descriptions of how to use their functions properly. |
| 33 | # take a look at /usr/portage/eclasses/ for more examples. |
34 | # take a look at /usr/portage/eclasses/ for more examples. |
| 34 | |
35 | |
| 35 | # Short one-line description of this package. |
36 | # Short one-line description of this package. |
| … | |
… | |
| 93 | # >=dev-lang/perl-5.6.1-r1 |
94 | # >=dev-lang/perl-5.6.1-r1 |
| 94 | # It is advisable to use the >= syntax show above, to reflect what you |
95 | # It is advisable to use the >= syntax show above, to reflect what you |
| 95 | # had installed on your system when you tested the package. Then |
96 | # had installed on your system when you tested the package. Then |
| 96 | # other users hopefully won't be caught without the right version of |
97 | # other users hopefully won't be caught without the right version of |
| 97 | # a dependency. |
98 | # a dependency. |
| 98 | DEPEND="" |
99 | #DEPEND="" |
| 99 | |
100 | |
| 100 | # Run-time dependencies. Must be defined to whatever this depends on to run. |
101 | # Run-time dependencies. Must be defined to whatever this depends on to run. |
| 101 | # The below is valid if the same run-time depends are required to compile. |
102 | # The below is valid if the same run-time depends are required to compile. |
| 102 | RDEPEND="${DEPEND}" |
103 | RDEPEND="${DEPEND}" |
| 103 | |
104 | |
| … | |
… | |
| 105 | # unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P} |
106 | # unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P} |
| 106 | # If you don't need to change it, leave the S= line out of the ebuild |
107 | # If you don't need to change it, leave the S= line out of the ebuild |
| 107 | # to keep it tidy. |
108 | # to keep it tidy. |
| 108 | #S="${WORKDIR}/${P}" |
109 | #S="${WORKDIR}/${P}" |
| 109 | |
110 | |
|
|
111 | |
|
|
112 | # The following src_compile function is implemented as default by portage, so |
|
|
113 | # you only need to call it, if you need a different behaviour. |
| 110 | src_compile() { |
114 | #src_compile() { |
| 111 | # Most open-source packages use GNU autoconf for configuration. |
115 | # Most open-source packages use GNU autoconf for configuration. |
| 112 | # The quickest (and preferred) way of running configure is: |
116 | # The default, quickest (and preferred) way of running configure is: |
| 113 | econf || die "econf failed" |
117 | #econf |
| 114 | # |
118 | # |
| 115 | # You could use something similar to the following lines to |
119 | # You could use something similar to the following lines to |
| 116 | # configure your package before compilation. The "|| die" portion |
120 | # configure your package before compilation. The "|| die" portion |
| 117 | # at the end will stop the build process if the command fails. |
121 | # at the end will stop the build process if the command fails. |
| 118 | # You should use this at the end of critical commands in the build |
122 | # You should use this at the end of critical commands in the build |
| … | |
… | |
| 132 | # builds (especially on SMP systems). Try emake first. It might |
136 | # builds (especially on SMP systems). Try emake first. It might |
| 133 | # not work for some packages, because some makefiles have bugs |
137 | # not work for some packages, because some makefiles have bugs |
| 134 | # related to parallelism, in these cases, use emake -j1 to limit |
138 | # related to parallelism, in these cases, use emake -j1 to limit |
| 135 | # make to a single process. The -j1 is a visual clue to others |
139 | # make to a single process. The -j1 is a visual clue to others |
| 136 | # that the makefiles have bugs that have been worked around. |
140 | # that the makefiles have bugs that have been worked around. |
|
|
141 | |
| 137 | emake || die "emake failed" |
142 | #emake || die "emake failed" |
| 138 | } |
143 | #} |
| 139 | |
144 | |
| 140 | src_install() { |
145 | src_install() { |
| 141 | # You must *personally verify* that this trick doesn't install |
146 | # You must *personally verify* that this trick doesn't install |
| 142 | # anything outside of DESTDIR; do this by reading and |
147 | # anything outside of DESTDIR; do this by reading and |
| 143 | # understanding the install part of the Makefiles. |
148 | # understanding the install part of the Makefiles. |
Parent Directory
| 
Revision Log
| 
Patch