/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.4 Revision 1.22
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 or later 2# Distributed under the terms of the GNU General Public License v2
3# Maintainer: First Last <your email>
4# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.4 2002/03/12 16:05:09 tod Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.22 2003/07/18 19:54:38 vapier Exp $
5 4
6# NOTE: The comments in this file are for instruction and 5# NOTE: The comments in this file are for instruction and documentation.
7# documentation. They're not meant to appear with your final, 6# They're not meant to appear with your final, production ebuild. Please
8# production ebuild. Please remember to remove them before submitting 7# remember to remove them before submitting or committing your ebuild. That
9# or committing your ebuild. That doesn't mean you can't add your own 8# doesn't mean you can't add your own comments though.
10# comments though.
11 9
12# Remember to add the proper Author line, above.
13
14# The 'Header' on the fourth line should just be left alone. 10# The 'Header' on the third line should just be left alone. When your ebuild
15# When your ebuild will be commited to cvs, the details on that line will 11# will be committed to cvs, the details on that line will be automatically
16# be automatically generated to contain the correct data. 12# generated to contain the correct data.
17
18# Source directory; the dir where the sources can be found
19# (automatically unpacked) inside ${WORKDIR}. Usually you can just
20# leave this as-is.
21S=${WORKDIR}/${P}
22 13
23# Short one-line description of this package. 14# Short one-line description of this package.
24DESCRIPTION="This is a sample skeleton ebuild file" 15DESCRIPTION="This is a sample skeleton ebuild file"
25 16
17# Homepage, not used by Portage directly but handy for developer reference
18HOMEPAGE="http://foo.bar.com/"
19
26# Point to any required sources; these will be automatically 20# Point to any required sources; these will be automatically downloaded by
27# downloaded by Portage. 21# Portage.
28SRC_URI="ftp://foo.bar.com/${P}.tar.gz" 22SRC_URI="ftp://foo.bar.com/${P}.tar.gz"
29 23
30# Homepage, not used by Portage directly but handy for developer reference 24# License of the package. This must match the name of file(s) in
31HOMEPAGE="http://" 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", "~sparc"
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# For binary packages, use -* and then list the archs the bin package
55# exists for. If the package was for an x86 binary package, then
56# KEYWORDS would be set like this: KEYWORDS="-* x86"
57# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
58# compatibility reasons.
59KEYWORDS="~x86"
60
61# Comprehensive list of any and all USE flags leveraged in the ebuild,
62# with the exception of any ARCH specific flags, i.e. "ppc", "sparc",
63# "sparc", "x86" and "alpha". This is a required variable. If the
64# ebuild doesn't use any USE flags, set to "".
65IUSE="X gnome"
32 66
33# Build-time dependencies, such as 67# Build-time dependencies, such as
34# ssl? ( >=openssl-0.9.6b ) 68# ssl? ( >=openssl-0.9.6b )
35# >=perl-5.6.1-r1 69# >=perl-5.6.1-r1
36# It is advisable to use the >= syntax show above, to reflect what you 70# It is advisable to use the >= syntax show above, to reflect what you
39# a dependency. 73# a dependency.
40DEPEND="" 74DEPEND=""
41 75
42# Run-time dependencies, same as DEPEND if RDEPEND isn't defined: 76# Run-time dependencies, same as DEPEND if RDEPEND isn't defined:
43#RDEPEND="" 77#RDEPEND=""
78
79# Source directory; the dir where the sources can be found (automatically
80# unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P}
81# if you omit this line.
82S=${WORKDIR}/${P}
44 83
45src_compile() { 84src_compile() {
46 # Most open-source packages use GNU autoconf for configuration. 85 # Most open-source packages use GNU autoconf for configuration.
47 # You should use something similar to the following lines to 86 # You should use something similar to the following lines to
48 # configure your package before compilation. The "|| die" portion 87 # configure your package before compilation. The "|| die" portion
56 --infodir=/usr/share/info \ 95 --infodir=/usr/share/info \
57 --mandir=/usr/share/man || die "./configure failed" 96 --mandir=/usr/share/man || die "./configure failed"
58 # Note the use of --infodir and --mandir, above. This is to make 97 # Note the use of --infodir and --mandir, above. This is to make
59 # this package FHS 2.2-compliant. For more information, see 98 # this package FHS 2.2-compliant. For more information, see
60 # http://www.pathname.com/fhs/ 99 # http://www.pathname.com/fhs/
61 100
101 # Also note that it is cleaner and easier to use econf, which is the
102 # portage shortcut to the above ./configure statement:
103 #
104 # econf || die
105 # Note that econf will die on failure, but plase use econf || die
106 # for consistency.
107
62 # emake (previously known as pmake) is a script that calls the 108 # emake (previously known as pmake) is a script that calls the
63 # standard GNU make with parallel building options for speedier 109 # standard GNU make with parallel building options for speedier
64 # builds (especially on SMP systems). Try emake first. It might 110 # builds (especially on SMP systems). Try emake first. It might
65 # not work for some packages, in which case you'll have to resort 111 # not work for some packages, in which case you'll have to resort
66 # to normal "make". 112 # to normal "make".
67 emake || die 113 emake || die
68 #make || die 114 #make || die
69} 115}
70 116
71src_install () { 117src_install() {
72 # You must *personally verify* that this trick doesn't install 118 # You must *personally verify* that this trick doesn't install
73 # anything outside of DESTDIR; do this by reading and 119 # anything outside of DESTDIR; do this by reading and
74 # understanding the install part of the Makefiles. 120 # understanding the install part of the Makefiles.
75 make DESTDIR=${D} install || die 121 make DESTDIR=${D} install || die
76 # For Makefiles that don't make proper use of DESTDIR, setting 122 # For Makefiles that don't make proper use of DESTDIR, setting
77 # prefix is often an alternative. However if you do this, then 123 # prefix is often an alternative. However if you do this, then
78 # you also need to specify mandir and infodir, since they were 124 # you also need to specify mandir and infodir, since they were
79 # passed to ./configure as absolute paths (overriding the prefix 125 # passed to ./configure as absolute paths (overriding the prefix
83 # mandir=${D}/usr/share/man \ 129 # mandir=${D}/usr/share/man \
84 # infodir=${D}/usr/share/info \ 130 # infodir=${D}/usr/share/info \
85 # install || die 131 # install || die
86 # Again, verify the Makefiles! We don't want anything falling 132 # Again, verify the Makefiles! We don't want anything falling
87 # outside of ${D}. 133 # outside of ${D}.
134
135 # The portage shortcut to the above command is simply:
136 #
137 #einstall || die
138 # Note that einstall will die on failure, but please use einstall || die
139 # for consistency.
88} 140}

Legend:
Removed from v.1.4  
changed lines
  Added in v.1.22

  ViewVC Help
Powered by ViewVC 1.1.20