/[gentoo-x86]/skel.ebuild
Gentoo

Contents of /skel.ebuild

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.10 - (show annotations) (download)
Thu Jul 11 12:42:35 2002 UTC (12 years ago) by blizzy
Branch: MAIN
Changes since 1.9: +1 -1 lines
fixed bug in KEYWORDS instructions, closes bug #4833

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 # 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="1"
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 KEYWORDS="*".
51 KEYWORDS="x86"
52
53 # Build-time dependencies, such as
54 # ssl? ( >=openssl-0.9.6b )
55 # >=perl-5.6.1-r1
56 # It is advisable to use the >= syntax show above, to reflect what you
57 # had installed on your system when you tested the package. Then
58 # other users hopefully won't be caught without the right version of
59 # a dependency.
60 DEPEND=""
61
62 # Run-time dependencies, same as DEPEND if RDEPEND isn't defined:
63 #RDEPEND=""
64
65 # Source directory; the dir where the sources can be found (automatically
66 # unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P}
67 # if you omit this line.
68
69 S=${WORKDIR}/${P}
70
71 src_compile() {
72 # Most open-source packages use GNU autoconf for configuration.
73 # You should use something similar to the following lines to
74 # configure your package before compilation. The "|| die" portion
75 # at the end will stop the build process if the command fails.
76 # You should use this at the end of critical commands in the build
77 # process. (Hint: Most commands are critical, that is, the build
78 # process should abort if they aren't successful.)
79 ./configure \
80 --host=${CHOST} \
81 --prefix=/usr \
82 --infodir=/usr/share/info \
83 --mandir=/usr/share/man || die "./configure failed"
84 # Note the use of --infodir and --mandir, above. This is to make
85 # this package FHS 2.2-compliant. For more information, see
86 # http://www.pathname.com/fhs/
87
88 # emake (previously known as pmake) is a script that calls the
89 # standard GNU make with parallel building options for speedier
90 # builds (especially on SMP systems). Try emake first. It might
91 # not work for some packages, in which case you'll have to resort
92 # to normal "make".
93 emake || die
94 #make || die
95 }
96
97 src_install () {
98 # You must *personally verify* that this trick doesn't install
99 # anything outside of DESTDIR; do this by reading and
100 # understanding the install part of the Makefiles.
101 make DESTDIR=${D} install || die
102 # For Makefiles that don't make proper use of DESTDIR, setting
103 # prefix is often an alternative. However if you do this, then
104 # you also need to specify mandir and infodir, since they were
105 # passed to ./configure as absolute paths (overriding the prefix
106 # setting).
107 #make \
108 # prefix=${D}/usr \
109 # mandir=${D}/usr/share/man \
110 # infodir=${D}/usr/share/info \
111 # install || die
112 # Again, verify the Makefiles! We don't want anything falling
113 # outside of ${D}.
114 }

  ViewVC Help
Powered by ViewVC 1.1.20