/[gentoo-x86]/skel.ebuild
Gentoo

Contents of /skel.ebuild

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.14 - (show annotations) (download)
Sat Oct 5 20:30:53 2002 UTC (11 years, 11 months ago) by gerk
Branch: MAIN
Changes since 1.13: +5 -0 lines
updated for IUSE information

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

  ViewVC Help
Powered by ViewVC 1.1.20