| 1 | # Copyright 1999-2002 Gentoo Technologies, Inc. |
1 | # Copyright 1999-2003 Gentoo Technologies, Inc. |
| 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.16 2002/10/24 06:08:47 vapier Exp $ |
3 | # $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.21 2003/05/20 22:55:06 msterret 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. |
| 9 | |
9 | |
| 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 commited 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 | # Short one-line description of this package. |
14 | # Short one-line description of this package. |
| 15 | DESCRIPTION="This is a sample skeleton ebuild file" |
15 | DESCRIPTION="This is a sample skeleton ebuild file" |
| 16 | |
16 | |
| … | |
… | |
| 41 | |
41 | |
| 42 | # Using KEYWORDS, we can record masking information *inside* an ebuild |
42 | # Using KEYWORDS, we can record masking information *inside* an ebuild |
| 43 | # instead of relying on an external package.mask file. Right now, you |
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 |
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 |
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 |
46 | # 5 official architecture names right now: "~x86", "~ppc", "~sparc", "~sparc64" |
|
|
47 | # and "~alpha". The ~ in front of the architecture indicates that the |
|
|
48 | # package is new and should be considered unstable until testing proves its |
|
|
49 | # stability. Once packages go stable the ~ prefix is removed. |
| 47 | # "sparc64". So, if you've confirmed that your ebuild works on x86 and ppc, |
50 | # So, if you've confirmed that your ebuild works on x86 and ppc, |
| 48 | # you'd specify: KEYWORDS="x86 ppc" |
51 | # you'd specify: KEYWORDS="~x86 ~ppc" |
| 49 | # For packages that are platform-independant (like Java, PHP or Perl |
52 | # For packages that are platform-independent (like Java, PHP or Perl |
| 50 | # applications) specify all keywords. |
53 | # applications) specify all keywords. |
| 51 | # DO NOT USE KEYWORDS="*". This is deprecated and only for backward |
54 | # DO NOT USE KEYWORDS="*". This is deprecated and only for backward |
| 52 | # compatibility reasons. |
55 | # compatibility reasons. |
| 53 | KEYWORDS="x86" |
56 | KEYWORDS="~x86" |
| 54 | |
57 | |
| 55 | # Comprehensive list of any and all USE flags leveraged in the ebuild, |
58 | # 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", |
59 | # with the exception of any ARCH specific flags, i.e. "ppc", "sparc", |
| 57 | # "sparc64", "x86" and "alpha". This is a required variable. If the |
60 | # "sparc64", "x86" and "alpha". This is a required variable. If the |
| 58 | # ebuild doesn't use any USE flags, set to "". |
61 | # ebuild doesn't use any USE flags, set to "". |
| … | |
… | |
| 71 | #RDEPEND="" |
74 | #RDEPEND="" |
| 72 | |
75 | |
| 73 | # Source directory; the dir where the sources can be found (automatically |
76 | # Source directory; the dir where the sources can be found (automatically |
| 74 | # unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P} |
77 | # unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P} |
| 75 | # if you omit this line. |
78 | # if you omit this line. |
| 76 | S="${WORKDIR}/${P}" |
79 | S=${WORKDIR}/${P} |
| 77 | |
80 | |
| 78 | src_compile() { |
81 | src_compile() { |
| 79 | # Most open-source packages use GNU autoconf for configuration. |
82 | # Most open-source packages use GNU autoconf for configuration. |
| 80 | # You should use something similar to the following lines to |
83 | # You should use something similar to the following lines to |
| 81 | # configure your package before compilation. The "|| die" portion |
84 | # configure your package before compilation. The "|| die" portion |
| … | |
… | |
| 89 | --infodir=/usr/share/info \ |
92 | --infodir=/usr/share/info \ |
| 90 | --mandir=/usr/share/man || die "./configure failed" |
93 | --mandir=/usr/share/man || die "./configure failed" |
| 91 | # Note the use of --infodir and --mandir, above. This is to make |
94 | # Note the use of --infodir and --mandir, above. This is to make |
| 92 | # this package FHS 2.2-compliant. For more information, see |
95 | # this package FHS 2.2-compliant. For more information, see |
| 93 | # http://www.pathname.com/fhs/ |
96 | # http://www.pathname.com/fhs/ |
|
|
97 | |
|
|
98 | # Also note that it is cleaner and easier to use econf, which is the |
|
|
99 | # portage shortcut to the above ./configure statement: |
|
|
100 | # |
|
|
101 | # econf || die |
|
|
102 | # Note that econf will die on failure, but plase use econf || die |
|
|
103 | # for consistency. |
| 94 | |
104 | |
| 95 | # emake (previously known as pmake) is a script that calls the |
105 | # emake (previously known as pmake) is a script that calls the |
| 96 | # standard GNU make with parallel building options for speedier |
106 | # standard GNU make with parallel building options for speedier |
| 97 | # builds (especially on SMP systems). Try emake first. It might |
107 | # builds (especially on SMP systems). Try emake first. It might |
| 98 | # not work for some packages, in which case you'll have to resort |
108 | # not work for some packages, in which case you'll have to resort |
| … | |
… | |
| 116 | # mandir=${D}/usr/share/man \ |
126 | # mandir=${D}/usr/share/man \ |
| 117 | # infodir=${D}/usr/share/info \ |
127 | # infodir=${D}/usr/share/info \ |
| 118 | # install || die |
128 | # install || die |
| 119 | # Again, verify the Makefiles! We don't want anything falling |
129 | # Again, verify the Makefiles! We don't want anything falling |
| 120 | # outside of ${D}. |
130 | # outside of ${D}. |
|
|
131 | |
|
|
132 | # The portage shortcut to the above command is simply: |
|
|
133 | # |
|
|
134 | #einstall || die |
|
|
135 | # Note that einstall will die on failure, but please use einstall || die |
|
|
136 | # for consistency. |
| 121 | } |
137 | } |