| 1 | # Copyright 1999-2000 Gentoo Technologies, Inc. |
1 | # Copyright 1999-2002 Gentoo Technologies, Inc. |
| 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 | # Author Your Name <your email> |
|
|
| 4 | # $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.1 2000/10/09 18:00:52 achim Exp $ |
3 | # $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.15 2002/10/18 18:52:09 blizzy Exp $ |
| 5 | |
4 | |
| 6 | #P= |
5 | # NOTE: The comments in this file are for instruction and documentation. |
| 7 | A=${P}.tar.gz |
6 | # They're not meant to appear with your final, production ebuild. Please |
| 8 | S=${WORKDIR}/${P} |
7 | # remember to remove them before submitting or committing your ebuild. That |
| 9 | DESCRIPTION="" |
8 | # doesn't mean you can't add your own comments though. |
| 10 | SRC_URI="ftp://" |
|
|
| 11 | HOMEPAGE="http://" |
|
|
| 12 | |
9 | |
|
|
10 | # The 'Header' on the third line should just be left alone. When your ebuild |
|
|
11 | # will be commited to cvs, the details on that line will be automatically |
|
|
12 | # generated to contain the correct data. |
|
|
13 | |
|
|
14 | # Short one-line description of this package. |
|
|
15 | DESCRIPTION="This is a sample skeleton ebuild file" |
|
|
16 | |
|
|
17 | # Homepage, not used by Portage directly but handy for developer reference |
|
|
18 | HOMEPAGE="http://foo.bar.com" |
|
|
19 | |
|
|
20 | # Point to any required sources; these will be automatically downloaded by |
|
|
21 | # Portage. |
|
|
22 | SRC_URI="ftp://foo.bar.com/${P}.tar.gz" |
|
|
23 | |
|
|
24 | # License of the package. This must match the name of file(s) in |
|
|
25 | # /usr/portage/licenses/. For complex license combination see the developer |
|
|
26 | # docs on gentoo.org for details. |
|
|
27 | LICENSE="" |
|
|
28 | |
|
|
29 | # The SLOT variable is used to tell Portage if it's OK to keep multiple |
|
|
30 | # versions of the same package installed at the same time. For example, |
|
|
31 | # if we have a libfoo-1.2.2 and libfoo-1.3.2 (which is not compatible |
|
|
32 | # with 1.2.2), it would be optimal to instruct Portage to not remove |
|
|
33 | # libfoo-1.2.2 if we decide to upgrade to libfoo-1.3.2. To do this, |
|
|
34 | # we specify SLOT="1.2" in libfoo-1.2.2 and SLOT="1.3" in libfoo-1.3.2. |
|
|
35 | # emerge clean understands SLOTs, and will keep the most recent version |
|
|
36 | # of each SLOT and remove everything else. |
|
|
37 | # Note that normal applications should use SLOT="0" if possible, since |
|
|
38 | # there should only be exactly one version installed at a time. |
|
|
39 | # DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package. |
|
|
40 | SLOT="0" |
|
|
41 | |
|
|
42 | # Using KEYWORDS, we can record masking information *inside* an ebuild |
|
|
43 | # instead of relying on an external package.mask file. Right now, you |
|
|
44 | # should set the KEYWORDS variable for every ebuild so that it contains |
|
|
45 | # the names of all the architectures with which the ebuild works. We have |
|
|
46 | # 4 official architecture names right now: "x86", "ppc", "sparc" and |
|
|
47 | # "sparc64". So, if you've confirmed that your ebuild works on x86 and ppc, |
|
|
48 | # you'd specify: KEYWORDS="x86 ppc" |
|
|
49 | # For packages that are platform-independant (like Java, PHP or Perl |
|
|
50 | # applications) specify all keywords. |
|
|
51 | # DO NOT USE KEYWORDS="*". This is deprecated and only for backward |
|
|
52 | # compatibility reasons. |
|
|
53 | KEYWORDS="x86" |
|
|
54 | |
|
|
55 | # Comprehensive list of any and all USE flags leveraged in the ebuild, |
|
|
56 | # with the exception of any ARCH specific flags, i.e. "ppc", "sparc", |
|
|
57 | # "sparc64", "x86" and "alpha". This is a required variable. If the |
|
|
58 | # ebuild doesn't use any USE flags, set to "". |
|
|
59 | IUSE="X gnome" |
|
|
60 | |
|
|
61 | # Build-time dependencies, such as |
|
|
62 | # ssl? ( >=openssl-0.9.6b ) |
|
|
63 | # >=perl-5.6.1-r1 |
|
|
64 | # It is advisable to use the >= syntax show above, to reflect what you |
|
|
65 | # had installed on your system when you tested the package. Then |
|
|
66 | # other users hopefully won't be caught without the right version of |
|
|
67 | # a dependency. |
|
|
68 | DEPEND="" |
|
|
69 | |
|
|
70 | # Run-time dependencies, same as DEPEND if RDEPEND isn't defined: |
|
|
71 | #RDEPEND="" |
|
|
72 | |
|
|
73 | # Source directory; the dir where the sources can be found (automatically |
|
|
74 | # unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P} |
|
|
75 | # if you omit this line. |
|
|
76 | |
|
|
77 | S="${WORKDIR}/${P}" |
| 13 | |
78 | |
| 14 | src_compile() { |
79 | src_compile() { |
|
|
80 | # Most open-source packages use GNU autoconf for configuration. |
|
|
81 | # You should use something similar to the following lines to |
|
|
82 | # configure your package before compilation. The "|| die" portion |
|
|
83 | # at the end will stop the build process if the command fails. |
|
|
84 | # You should use this at the end of critical commands in the build |
|
|
85 | # process. (Hint: Most commands are critical, that is, the build |
|
|
86 | # process should abort if they aren't successful.) |
|
|
87 | ./configure \ |
|
|
88 | --host=${CHOST} \ |
|
|
89 | --prefix=/usr \ |
|
|
90 | --infodir=/usr/share/info \ |
|
|
91 | --mandir=/usr/share/man || die "./configure failed" |
|
|
92 | # Note the use of --infodir and --mandir, above. This is to make |
|
|
93 | # this package FHS 2.2-compliant. For more information, see |
|
|
94 | # http://www.pathname.com/fhs/ |
| 15 | |
95 | |
| 16 | cd ${S} |
96 | # emake (previously known as pmake) is a script that calls the |
| 17 | try ./configure --prefix=/usr --host=${CHOST} |
97 | # standard GNU make with parallel building options for speedier |
| 18 | try make |
98 | # builds (especially on SMP systems). Try emake first. It might |
| 19 | |
99 | # not work for some packages, in which case you'll have to resort |
|
|
100 | # to normal "make". |
|
|
101 | emake || die |
|
|
102 | #make || die |
| 20 | } |
103 | } |
| 21 | |
104 | |
| 22 | src_install () { |
105 | src_install() { |
| 23 | |
106 | # You must *personally verify* that this trick doesn't install |
| 24 | cd ${S} |
107 | # anything outside of DESTDIR; do this by reading and |
|
|
108 | # understanding the install part of the Makefiles. |
| 25 | try make DESTDIR=${D} install |
109 | make DESTDIR=${D} install || die |
| 26 | |
110 | # For Makefiles that don't make proper use of DESTDIR, setting |
|
|
111 | # prefix is often an alternative. However if you do this, then |
|
|
112 | # you also need to specify mandir and infodir, since they were |
|
|
113 | # passed to ./configure as absolute paths (overriding the prefix |
|
|
114 | # setting). |
|
|
115 | #make \ |
|
|
116 | # prefix=${D}/usr \ |
|
|
117 | # mandir=${D}/usr/share/man \ |
|
|
118 | # infodir=${D}/usr/share/info \ |
|
|
119 | # install || die |
|
|
120 | # Again, verify the Makefiles! We don't want anything falling |
|
|
121 | # outside of ${D}. |
| 27 | } |
122 | } |
| 28 | |
|
|