/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.1 Revision 1.21
1# Copyright 1999-2000 Gentoo Technologies, Inc. 1# Copyright 1999-2003 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.21 2003/05/20 22:55:06 msterret Exp $
5 4
6#P= 5# NOTE: The comments in this file are for instruction and documentation.
7A=${P}.tar.gz 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 committed 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.
15DESCRIPTION="This is a sample skeleton ebuild file"
16
17# Homepage, not used by Portage directly but handy for developer reference
18HOMEPAGE="http://foo.bar.com/"
19
20# Point to any required sources; these will be automatically downloaded by
21# Portage.
22SRC_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.
27LICENSE=""
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.
40SLOT="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# 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.
50# So, if you've confirmed that your ebuild works on x86 and ppc,
51# you'd specify: KEYWORDS="~x86 ~ppc"
52# For packages that are platform-independent (like Java, PHP or Perl
53# applications) specify all keywords.
54# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
55# compatibility reasons.
56KEYWORDS="~x86"
57
58# Comprehensive list of any and all USE flags leveraged in the ebuild,
59# with the exception of any ARCH specific flags, i.e. "ppc", "sparc",
60# "sparc64", "x86" and "alpha". This is a required variable. If the
61# ebuild doesn't use any USE flags, set to "".
62IUSE="X gnome"
63
64# Build-time dependencies, such as
65# ssl? ( >=openssl-0.9.6b )
66# >=perl-5.6.1-r1
67# It is advisable to use the >= syntax show above, to reflect what you
68# had installed on your system when you tested the package. Then
69# other users hopefully won't be caught without the right version of
70# a dependency.
71DEPEND=""
72
73# Run-time dependencies, same as DEPEND if RDEPEND isn't defined:
74#RDEPEND=""
75
76# Source directory; the dir where the sources can be found (automatically
77# unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P}
78# if you omit this line.
8S=${WORKDIR}/${P} 79S=${WORKDIR}/${P}
9DESCRIPTION=""
10SRC_URI="ftp://"
11HOMEPAGE="http://"
12
13 80
14src_compile() { 81src_compile() {
82 # Most open-source packages use GNU autoconf for configuration.
83 # You should use something similar to the following lines to
84 # configure your package before compilation. The "|| die" portion
85 # at the end will stop the build process if the command fails.
86 # You should use this at the end of critical commands in the build
87 # process. (Hint: Most commands are critical, that is, the build
88 # process should abort if they aren't successful.)
89 ./configure \
90 --host=${CHOST} \
91 --prefix=/usr \
92 --infodir=/usr/share/info \
93 --mandir=/usr/share/man || die "./configure failed"
94 # Note the use of --infodir and --mandir, above. This is to make
95 # this package FHS 2.2-compliant. For more information, see
96 # http://www.pathname.com/fhs/
15 97
16 cd ${S} 98 # Also note that it is cleaner and easier to use econf, which is the
17 try ./configure --prefix=/usr --host=${CHOST} 99 # portage shortcut to the above ./configure statement:
18 try make 100 #
101 # econf || die
102 # Note that econf will die on failure, but plase use econf || die
103 # for consistency.
19 104
105 # emake (previously known as pmake) is a script that calls the
106 # standard GNU make with parallel building options for speedier
107 # builds (especially on SMP systems). Try emake first. It might
108 # not work for some packages, in which case you'll have to resort
109 # to normal "make".
110 emake || die
111 #make || die
20} 112}
21 113
22src_install () { 114src_install() {
115 # You must *personally verify* that this trick doesn't install
116 # anything outside of DESTDIR; do this by reading and
117 # understanding the install part of the Makefiles.
118 make DESTDIR=${D} install || die
119 # For Makefiles that don't make proper use of DESTDIR, setting
120 # prefix is often an alternative. However if you do this, then
121 # you also need to specify mandir and infodir, since they were
122 # passed to ./configure as absolute paths (overriding the prefix
123 # setting).
124 #make \
125 # prefix=${D}/usr \
126 # mandir=${D}/usr/share/man \
127 # infodir=${D}/usr/share/info \
128 # install || die
129 # Again, verify the Makefiles! We don't want anything falling
130 # outside of ${D}.
23 131
24 cd ${S} 132 # The portage shortcut to the above command is simply:
25 try make DESTDIR=${D} install 133 #
26 134 #einstall || die
135 # Note that einstall will die on failure, but please use einstall || die
136 # for consistency.
27} 137}
28

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.21

  ViewVC Help
Powered by ViewVC 1.1.20