1 | # Copyright 1999-2002 Gentoo Technologies, Inc. |
1 | # Copyright 1999-2011 Gentoo Foundation |
2 | # Distributed under the terms of the GNU General Public License, v2 or later |
2 | # Distributed under the terms of the GNU General Public License v2 |
3 | # Maintainer: First Last <your email> |
|
|
4 | # $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.5 2002/04/29 22:56:53 sandymac Exp $ |
3 | # $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.55 2011/01/01 00:01:45 abcd Exp $ |
5 | |
4 | |
6 | # NOTE: The comments in this file are for instruction and |
5 | # NOTE: The comments in this file are for instruction and documentation. |
7 | # documentation. They're not meant to appear with your final, |
6 | # They're not meant to appear with your final, production ebuild. Please |
8 | # production ebuild. Please remember to remove them before submitting |
7 | # remember to remove them before submitting or committing your ebuild. That |
9 | # or committing your ebuild. That doesn't mean you can't add your own |
8 | # doesn't mean you can't add your own comments though. |
10 | # comments though. |
|
|
11 | |
9 | |
12 | # Remember to add the proper Author line, above. |
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 |
|
|
12 | # generated to contain the correct data. |
13 | |
13 | |
14 | # The 'Header' on the fourth line should just be left alone. |
14 | # The EAPI variable tells the ebuild format in use. |
15 | # When your ebuild will be commited to cvs, the details on that line will |
15 | # Defaults to 0 if not specified. The current PMS draft contains details on |
16 | # be automatically generated to contain the correct data. |
16 | # a proposed EAPI=0 definition but is not finalized yet. |
|
|
17 | # Eclasses will test for this variable if they need to use EAPI > 0 features. |
|
|
18 | #EAPI=0 |
17 | |
19 | |
18 | # Source directory; the dir where the sources can be found |
20 | # inherit lists eclasses to inherit functions from. Almost all ebuilds should |
19 | # (automatically unpacked) inside ${WORKDIR}. Usually you can just |
21 | # inherit eutils, as a large amount of important functionality has been |
20 | # leave this as-is. |
22 | # moved there. For example, the epatch call mentioned below wont work |
21 | S=${WORKDIR}/${P} |
23 | # without the following line: |
|
|
24 | inherit eutils |
|
|
25 | # A well-used example of an eclass function that needs eutils is epatch. If |
|
|
26 | # your source needs patches applied, it's suggested to put your patch in the |
|
|
27 | # 'files' directory and use: |
|
|
28 | # |
|
|
29 | # epatch "${FILESDIR}"/patch-name-here |
|
|
30 | # |
|
|
31 | # eclasses tend to list descriptions of how to use their functions properly. |
|
|
32 | # take a look at /usr/portage/eclasses/ for more examples. |
22 | |
33 | |
23 | # Short one-line description of this package. |
34 | # Short one-line description of this package. |
24 | DESCRIPTION="This is a sample skeleton ebuild file" |
35 | DESCRIPTION="This is a sample skeleton ebuild file" |
25 | |
36 | |
|
|
37 | # Homepage, not used by Portage directly but handy for developer reference |
|
|
38 | HOMEPAGE="http://foo.bar.com/" |
|
|
39 | |
26 | # Point to any required sources; these will be automatically |
40 | # Point to any required sources; these will be automatically downloaded by |
27 | # downloaded by Portage. |
41 | # Portage. |
28 | SRC_URI="ftp://foo.bar.com/${P}.tar.gz" |
42 | SRC_URI="ftp://foo.bar.com/${P}.tar.gz" |
29 | |
43 | |
30 | # Homepage, not used by Portage directly but handy for developer reference |
|
|
31 | HOMEPAGE="http://" |
|
|
32 | |
|
|
33 | # License of the package. This must match the name of file(s) in |
44 | # License of the package. This must match the name of file(s) in |
34 | # /usr/portage/licenses/. For complex license combination see the developer |
45 | # /usr/portage/licenses/. For complex license combination see the developer |
35 | # docs on gentoo.org for details. |
46 | # docs on gentoo.org for details. |
36 | LICENSE="" |
47 | LICENSE="" |
37 | |
48 | |
|
|
49 | # The SLOT variable is used to tell Portage if it's OK to keep multiple |
|
|
50 | # versions of the same package installed at the same time. For example, |
|
|
51 | # if we have a libfoo-1.2.2 and libfoo-1.3.2 (which is not compatible |
|
|
52 | # with 1.2.2), it would be optimal to instruct Portage to not remove |
|
|
53 | # libfoo-1.2.2 if we decide to upgrade to libfoo-1.3.2. To do this, |
|
|
54 | # we specify SLOT="1.2" in libfoo-1.2.2 and SLOT="1.3" in libfoo-1.3.2. |
|
|
55 | # emerge clean understands SLOTs, and will keep the most recent version |
|
|
56 | # of each SLOT and remove everything else. |
|
|
57 | # Note that normal applications should use SLOT="0" if possible, since |
|
|
58 | # there should only be exactly one version installed at a time. |
|
|
59 | # DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package. |
|
|
60 | SLOT="0" |
|
|
61 | |
|
|
62 | # Using KEYWORDS, we can record masking information *inside* an ebuild |
|
|
63 | # instead of relying on an external package.mask file. Right now, you should |
|
|
64 | # set the KEYWORDS variable for every ebuild so that it contains the names of |
|
|
65 | # all the architectures with which the ebuild works. All of the official |
|
|
66 | # architectures can be found in the keywords.desc file which is in |
|
|
67 | # /usr/portage/profiles/. Usually you should just set this to "~x86". The ~ |
|
|
68 | # in front of the architecture indicates that the package is new and should be |
|
|
69 | # considered unstable until testing proves its stability. So, if you've |
|
|
70 | # confirmed that your ebuild works on x86 and ppc, you'd specify: |
|
|
71 | # KEYWORDS="~x86 ~ppc" |
|
|
72 | # Once packages go stable, the ~ prefix is removed. |
|
|
73 | # For binary packages, use -* and then list the archs the bin package |
|
|
74 | # exists for. If the package was for an x86 binary package, then |
|
|
75 | # KEYWORDS would be set like this: KEYWORDS="-* x86" |
|
|
76 | # DO NOT USE KEYWORDS="*". This is deprecated and only for backward |
|
|
77 | # compatibility reasons. |
|
|
78 | KEYWORDS="~x86" |
|
|
79 | |
|
|
80 | # Comprehensive list of any and all USE flags leveraged in the ebuild, |
|
|
81 | # with the exception of any ARCH specific flags, i.e. "ppc", "sparc", |
|
|
82 | # "x86" and "alpha". This is a required variable. If the ebuild doesn't |
|
|
83 | # use any USE flags, set to "". |
|
|
84 | IUSE="gnome X" |
|
|
85 | |
|
|
86 | # A space delimited list of portage features to restrict. man 5 ebuild |
|
|
87 | # for details. Usually not needed. |
|
|
88 | #RESTRICT="strip" |
|
|
89 | |
38 | # Build-time dependencies, such as |
90 | # Build-time dependencies, such as |
39 | # ssl? ( >=openssl-0.9.6b ) |
91 | # ssl? ( >=dev-libs/openssl-0.9.6b ) |
40 | # >=perl-5.6.1-r1 |
92 | # >=dev-lang/perl-5.6.1-r1 |
41 | # It is advisable to use the >= syntax show above, to reflect what you |
93 | # It is advisable to use the >= syntax show above, to reflect what you |
42 | # had installed on your system when you tested the package. Then |
94 | # had installed on your system when you tested the package. Then |
43 | # other users hopefully won't be caught without the right version of |
95 | # other users hopefully won't be caught without the right version of |
44 | # a dependency. |
96 | # a dependency. |
45 | DEPEND="" |
97 | #DEPEND="" |
46 | |
98 | |
47 | # Run-time dependencies, same as DEPEND if RDEPEND isn't defined: |
99 | # Run-time dependencies. Must be defined to whatever this depends on to run. |
48 | #RDEPEND="" |
100 | # The below is valid if the same run-time depends are required to compile. |
|
|
101 | RDEPEND="${DEPEND}" |
49 | |
102 | |
|
|
103 | # Source directory; the dir where the sources can be found (automatically |
|
|
104 | # unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P} |
|
|
105 | # If you don't need to change it, leave the S= line out of the ebuild |
|
|
106 | # to keep it tidy. |
|
|
107 | #S="${WORKDIR}/${P}" |
|
|
108 | |
|
|
109 | |
|
|
110 | # The following src_compile function is implemented as default by portage, so |
|
|
111 | # you only need to call it, if you need a different behaviour. |
50 | src_compile() { |
112 | #src_compile() { |
51 | # Most open-source packages use GNU autoconf for configuration. |
113 | # Most open-source packages use GNU autoconf for configuration. |
|
|
114 | # The default, quickest (and preferred) way of running configure is: |
|
|
115 | #econf |
|
|
116 | # |
52 | # You should use something similar to the following lines to |
117 | # You could use something similar to the following lines to |
53 | # configure your package before compilation. The "|| die" portion |
118 | # configure your package before compilation. The "|| die" portion |
54 | # at the end will stop the build process if the command fails. |
119 | # at the end will stop the build process if the command fails. |
55 | # You should use this at the end of critical commands in the build |
120 | # You should use this at the end of critical commands in the build |
56 | # process. (Hint: Most commands are critical, that is, the build |
121 | # process. (Hint: Most commands are critical, that is, the build |
57 | # process should abort if they aren't successful.) |
122 | # process should abort if they aren't successful.) |
58 | ./configure \ |
123 | #./configure \ |
59 | --host=${CHOST} \ |
124 | # --host=${CHOST} \ |
60 | --prefix=/usr \ |
125 | # --prefix=/usr \ |
61 | --infodir=/usr/share/info \ |
126 | # --infodir=/usr/share/info \ |
62 | --mandir=/usr/share/man || die "./configure failed" |
127 | # --mandir=/usr/share/man || die "./configure failed" |
63 | # Note the use of --infodir and --mandir, above. This is to make |
128 | # Note the use of --infodir and --mandir, above. This is to make |
64 | # this package FHS 2.2-compliant. For more information, see |
129 | # this package FHS 2.2-compliant. For more information, see |
65 | # http://www.pathname.com/fhs/ |
130 | # http://www.pathname.com/fhs/ |
66 | |
131 | |
67 | # emake (previously known as pmake) is a script that calls the |
132 | # emake (previously known as pmake) is a script that calls the |
68 | # standard GNU make with parallel building options for speedier |
133 | # standard GNU make with parallel building options for speedier |
69 | # builds (especially on SMP systems). Try emake first. It might |
134 | # builds (especially on SMP systems). Try emake first. It might |
70 | # not work for some packages, in which case you'll have to resort |
135 | # not work for some packages, because some makefiles have bugs |
71 | # to normal "make". |
136 | # related to parallelism, in these cases, use emake -j1 to limit |
72 | emake || die |
137 | # make to a single process. The -j1 is a visual clue to others |
73 | #make || die |
138 | # that the makefiles have bugs that have been worked around. |
74 | } |
|
|
75 | |
139 | |
|
|
140 | #emake || die "emake failed" |
|
|
141 | #} |
|
|
142 | |
76 | src_install () { |
143 | src_install() { |
77 | # You must *personally verify* that this trick doesn't install |
144 | # You must *personally verify* that this trick doesn't install |
78 | # anything outside of DESTDIR; do this by reading and |
145 | # anything outside of DESTDIR; do this by reading and |
79 | # understanding the install part of the Makefiles. |
146 | # understanding the install part of the Makefiles. |
80 | make DESTDIR=${D} install || die |
147 | # This is the preferred way to install. |
|
|
148 | emake DESTDIR="${D}" install || die "emake install failed" |
|
|
149 | |
|
|
150 | # When you hit a failure with emake, do not just use make. It is |
|
|
151 | # better to fix the Makefiles to allow proper parallelization. |
|
|
152 | # If you fail with that, use "emake -j1", it's still better than make. |
|
|
153 | |
81 | # For Makefiles that don't make proper use of DESTDIR, setting |
154 | # For Makefiles that don't make proper use of DESTDIR, setting |
82 | # prefix is often an alternative. However if you do this, then |
155 | # prefix is often an alternative. However if you do this, then |
83 | # you also need to specify mandir and infodir, since they were |
156 | # you also need to specify mandir and infodir, since they were |
84 | # passed to ./configure as absolute paths (overriding the prefix |
157 | # passed to ./configure as absolute paths (overriding the prefix |
85 | # setting). |
158 | # setting). |
86 | #make \ |
159 | #emake \ |
87 | # prefix=${D}/usr \ |
160 | # prefix="${D}"/usr \ |
88 | # mandir=${D}/usr/share/man \ |
161 | # mandir="${D}"/usr/share/man \ |
89 | # infodir=${D}/usr/share/info \ |
162 | # infodir="${D}"/usr/share/info \ |
90 | # install || die |
163 | # libdir="${D}"/usr/$(get_libdir) \ |
|
|
164 | # install || die "emake install failed" |
91 | # Again, verify the Makefiles! We don't want anything falling |
165 | # Again, verify the Makefiles! We don't want anything falling |
92 | # outside of ${D}. |
166 | # outside of ${D}. |
|
|
167 | |
|
|
168 | # The portage shortcut to the above command is simply: |
|
|
169 | # |
|
|
170 | #einstall || die "einstall failed" |
93 | } |
171 | } |