| 1 |
# Copyright 1999-2004 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 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.
|
| 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="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 |
# 4 official architecture names right now: "~x86", "~ppc", "~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.
|
| 59 |
KEYWORDS="~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 |
# "x86" and "alpha". This is a required variable. If the
|
| 64 |
# ebuild doesn't use any USE flags, set to "".
|
| 65 |
IUSE="X gnome"
|
| 66 |
|
| 67 |
# Build-time dependencies, such as
|
| 68 |
# ssl? ( >=dev-libs/openssl-0.9.6b )
|
| 69 |
# >=dev-lang/perl-5.6.1-r1
|
| 70 |
# It is advisable to use the >= syntax show above, to reflect what you
|
| 71 |
# had installed on your system when you tested the package. Then
|
| 72 |
# other users hopefully won't be caught without the right version of
|
| 73 |
# a dependency.
|
| 74 |
DEPEND=""
|
| 75 |
|
| 76 |
# Run-time dependencies, same as DEPEND if RDEPEND isn't defined:
|
| 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.
|
| 82 |
S=${WORKDIR}/${P}
|
| 83 |
|
| 84 |
src_compile() {
|
| 85 |
# Most open-source packages use GNU autoconf for configuration.
|
| 86 |
# You should use something similar to the following lines to
|
| 87 |
# configure your package before compilation. The "|| die" portion
|
| 88 |
# at the end will stop the build process if the command fails.
|
| 89 |
# You should use this at the end of critical commands in the build
|
| 90 |
# process. (Hint: Most commands are critical, that is, the build
|
| 91 |
# process should abort if they aren't successful.)
|
| 92 |
./configure \
|
| 93 |
--host=${CHOST} \
|
| 94 |
--prefix=/usr \
|
| 95 |
--infodir=/usr/share/info \
|
| 96 |
--mandir=/usr/share/man || die "./configure failed"
|
| 97 |
# Note the use of --infodir and --mandir, above. This is to make
|
| 98 |
# this package FHS 2.2-compliant. For more information, see
|
| 99 |
# http://www.pathname.com/fhs/
|
| 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 |
|
| 108 |
# emake (previously known as pmake) is a script that calls the
|
| 109 |
# standard GNU make with parallel building options for speedier
|
| 110 |
# builds (especially on SMP systems). Try emake first. It might
|
| 111 |
# not work for some packages, in which case you'll have to resort
|
| 112 |
# to normal "make".
|
| 113 |
emake || die
|
| 114 |
#make || die
|
| 115 |
}
|
| 116 |
|
| 117 |
src_install() {
|
| 118 |
# You must *personally verify* that this trick doesn't install
|
| 119 |
# anything outside of DESTDIR; do this by reading and
|
| 120 |
# understanding the install part of the Makefiles.
|
| 121 |
make DESTDIR=${D} install || die
|
| 122 |
# For Makefiles that don't make proper use of DESTDIR, setting
|
| 123 |
# prefix is often an alternative. However if you do this, then
|
| 124 |
# you also need to specify mandir and infodir, since they were
|
| 125 |
# passed to ./configure as absolute paths (overriding the prefix
|
| 126 |
# setting).
|
| 127 |
#make \
|
| 128 |
# prefix=${D}/usr \
|
| 129 |
# mandir=${D}/usr/share/man \
|
| 130 |
# infodir=${D}/usr/share/info \
|
| 131 |
# install || die
|
| 132 |
# Again, verify the Makefiles! We don't want anything falling
|
| 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.
|
| 140 |
}
|
Parent Directory
| 
Revision Log