viewvc.cgi/gentoo-x86/skel.ebuild

# Copyright 1999-2006 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

# NOTE: The comments in this file are for instruction and documentation.  
# They're not meant to appear with your final, production ebuild.  Please
# remember to remove them before submitting or committing your ebuild.  That
# doesn't mean you can't add your own comments though.

# The 'Header' on the third line should just be left alone.  When your ebuild
# will be committed to cvs, the details on that line will be automatically
# generated to contain the correct data.

# inherit lists eclasses to inherit functions from. Almost all ebuilds should
# inherit eutils, as a large amount of important functionality has been
# moved there. For example, the $(get_libdir) mentioned below wont work
# without the following line:
inherit eutils
# A well-used example of an eclass function that needs eutils is epatch. If
# your source needs patches applied, it's suggested to put your patch in the
# 'files' directory and use:
#
#   epatch ${FILESDIR}/patch-name-here
#
# eclasses tend to list descriptions of how to use their functions properly.
# take a look at /usr/portage/eclasses/ for more examples.

# Short one-line description of this package.
DESCRIPTION="This is a sample skeleton ebuild file"

# Homepage, not used by Portage directly but handy for developer reference
HOMEPAGE="http://foo.bar.com/"

# Point to any required sources; these will be automatically downloaded by
# Portage.
SRC_URI="ftp://foo.bar.com/${P}.tar.gz"

# License of the package.  This must match the name of file(s) in
# /usr/portage/licenses/.  For complex license combination see the developer
# docs on gentoo.org for details.
LICENSE=""

# The SLOT variable is used to tell Portage if it's OK to keep multiple
# versions of the same package installed at the same time.  For example,
# if we have a libfoo-1.2.2 and libfoo-1.3.2 (which is not compatible
# with 1.2.2), it would be optimal to instruct Portage to not remove
# libfoo-1.2.2 if we decide to upgrade to libfoo-1.3.2.  To do this,
# we specify SLOT="1.2" in libfoo-1.2.2 and SLOT="1.3" in libfoo-1.3.2.
# emerge clean understands SLOTs, and will keep the most recent version
# of each SLOT and remove everything else.
# Note that normal applications should use SLOT="0" if possible, since
# there should only be exactly one version installed at a time.
# DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package.
SLOT="0"

# Using KEYWORDS, we can record masking information *inside* an ebuild 
# instead of relying on an external package.mask file.  Right now, you should 
# set the KEYWORDS variable for every ebuild so that it contains the names of 
# all the architectures with which the ebuild works.  All of the official 
# architectures can be found in the keywords.desc file which is in 
# /usr/portage/profiles/.  Usually you should just set this to "~x86".  The ~ 
# in front of the architecture indicates that the package is new and should be 
# considered unstable until testing proves its stability.  So, if you've 
# confirmed that your ebuild works on x86 and ppc, you'd specify: 
# KEYWORDS="~x86 ~ppc"
# Once packages go stable, the ~ prefix is removed.
# For binary packages, use -* and then list the archs the bin package
# exists for.  If the package was for an x86 binary package, then
# KEYWORDS would be set like this: KEYWORDS="-* x86"
# DO NOT USE KEYWORDS="*".  This is deprecated and only for backward
# compatibility reasons.
KEYWORDS="~x86"

# Comprehensive list of any and all USE flags leveraged in the ebuild,
# with the exception of any ARCH specific flags, i.e. "ppc", "sparc",
# "x86" and "alpha".  This is a required variable.  If the ebuild doesn't 
# use any USE flags, set to "".
IUSE="gnome X"

# A space delimited list of portage features to restrict. man 5 ebuild
# for details.  Usually not needed.
#RESTRICT="strip"

# Build-time dependencies, such as
#    ssl? ( >=dev-libs/openssl-0.9.6b )
#    >=dev-lang/perl-5.6.1-r1
# It is advisable to use the >= syntax show above, to reflect what you
# had installed on your system when you tested the package.  Then
# other users hopefully won't be caught without the right version of
# a dependency.
DEPEND=""

# Run-time dependencies, same as DEPEND if RDEPEND isn't defined:
#RDEPEND=""

# Source directory; the dir where the sources can be found (automatically
# unpacked) inside ${WORKDIR}.  The default value for S is ${WORKDIR}/${P}
# If you don't need to change it, leave the S= line out of the ebuild
# to keep it tidy.
S=${WORKDIR}/${P}

src_compile() {
        # Most open-source packages use GNU autoconf for configuration.
        # The quickest (and preferred) way of running configure is:
        econf || die "econf failed"
        #
        # You could use something similar to the following lines to
        # configure your package before compilation.  The "|| die" portion
        # at the end will stop the build process if the command fails.
        # You should use this at the end of critical commands in the build
        # process.  (Hint: Most commands are critical, that is, the build
        # process should abort if they aren't successful.)
        #./configure \
        #       --host=${CHOST} \
        #       --prefix=/usr \
        #       --infodir=/usr/share/info \
        #       --mandir=/usr/share/man || die "./configure failed"
        # Note the use of --infodir and --mandir, above. This is to make
        # this package FHS 2.2-compliant.  For more information, see
        #   http://www.pathname.com/fhs/

        # emake (previously known as pmake) is a script that calls the
        # standard GNU make with parallel building options for speedier
        # builds (especially on SMP systems).  Try emake first.  It might
        # not work for some packages, because some makefiles have bugs
        # related to parallelism, in these cases, use emake -j1 to limit
        # make to a single process.  The -j1 is a visual clue to others
        # that the makefiles have bugs that have been worked around.
        emake || die "emake failed"
}

src_install() {
        # You must *personally verify* that this trick doesn't install
        # anything outside of DESTDIR; do this by reading and
        # understanding the install part of the Makefiles.
        # This is the preferred way to install.
        emake DESTDIR="${D}" install || die "emake install failed"

        # When you hit a failure with emake, do not just use make. It is
        # better to fix the Makefiles to allow proper parallelization.
        # If you fail with that, use "emake -j1", it's still better than make.

        # For Makefiles that don't make proper use of DESTDIR, setting
        # prefix is often an alternative.  However if you do this, then
        # you also need to specify mandir and infodir, since they were
        # passed to ./configure as absolute paths (overriding the prefix
        # setting).
        #emake \
        #       prefix="${D}"/usr \
        #       mandir="${D}"/usr/share/man \
        #       infodir="${D}"/usr/share/info \
        #       libdir="${D}"/usr/$(get_libdir) \
        #       install || die "emake install failed"
        # Again, verify the Makefiles!  We don't want anything falling
        # outside of ${D}.

        # The portage shortcut to the above command is simply:
        #
        #einstall || die "einstall failed"
}
1	vapier	1.36	# Copyright 1999-2006 Gentoo Foundation
2	drobbins	1.6	# Distributed under the terms of the GNU General Public License v2
3	sandymac	1.8	# $Header: $
4	drobbins	1.6
5	vapier	1.27	# NOTE: The comments in this file are for instruction and documentation.
6	drobbins	1.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	msterret	1.21	# will be committed to cvs, the details on that line will be automatically
12	drobbins	1.6	# generated to contain the correct data.
13
14	lv	1.30	# inherit lists eclasses to inherit functions from. Almost all ebuilds should
15			# inherit eutils, as a large amount of important functionality has been
16			# moved there. For example, the $(get_libdir) mentioned below wont work
17			# without the following line:
18			inherit eutils
19			# A well-used example of an eclass function that needs eutils is epatch. If
20			# your source needs patches applied, it's suggested to put your patch in the
21			# 'files' directory and use:
22			#
23			# epatch ${FILESDIR}/patch-name-here
24			#
25			# eclasses tend to list descriptions of how to use their functions properly.
26			# take a look at /usr/portage/eclasses/ for more examples.
27
28	gbevin	1.3	# Short one-line description of this package.
29			DESCRIPTION="This is a sample skeleton ebuild file"
30
31			# Homepage, not used by Portage directly but handy for developer reference
32	vapier	1.16	HOMEPAGE="http://foo.bar.com/"
33	blizzy	1.9
34			# Point to any required sources; these will be automatically downloaded by
35			# Portage.
36			SRC_URI="ftp://foo.bar.com/${P}.tar.gz"
37	sandymac	1.5
38	vapier	1.27	# License of the package. This must match the name of file(s) in
39			# /usr/portage/licenses/. For complex license combination see the developer
40	sandymac	1.5	# docs on gentoo.org for details.
41			LICENSE=""
42	achim	1.1
43	blizzy	1.9	# The SLOT variable is used to tell Portage if it's OK to keep multiple
44	vapier	1.27	# versions of the same package installed at the same time. For example,
45	blizzy	1.9	# if we have a libfoo-1.2.2 and libfoo-1.3.2 (which is not compatible
46			# with 1.2.2), it would be optimal to instruct Portage to not remove
47	vapier	1.27	# libfoo-1.2.2 if we decide to upgrade to libfoo-1.3.2. To do this,
48	blizzy	1.9	# we specify SLOT="1.2" in libfoo-1.2.2 and SLOT="1.3" in libfoo-1.3.2.
49			# emerge clean understands SLOTs, and will keep the most recent version
50			# of each SLOT and remove everything else.
51			# Note that normal applications should use SLOT="0" if possible, since
52			# there should only be exactly one version installed at a time.
53			# DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package.
54	blizzy	1.12	SLOT="0"
55	blizzy	1.9
56	vapier	1.35	# Using KEYWORDS, we can record masking information inside an ebuild
57			# instead of relying on an external package.mask file. Right now, you should
58			# set the KEYWORDS variable for every ebuild so that it contains the names of
59			# all the architectures with which the ebuild works. All of the official
60			# architectures can be found in the keywords.desc file which is in
61			# /usr/portage/profiles/. Usually you should just set this to "~x86". The ~
62			# in front of the architecture indicates that the package is new and should be
63			# considered unstable until testing proves its stability. So, if you've
64			# confirmed that your ebuild works on x86 and ppc, you'd specify:
65			# KEYWORDS="~x86 ~ppc"
66			# Once packages go stable, the ~ prefix is removed.
67	vapier	1.22	# For binary packages, use -* and then list the archs the bin package
68			# exists for. If the package was for an x86 binary package, then
69			# KEYWORDS would be set like this: KEYWORDS="-* x86"
70	vapier	1.27	# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
71	blizzy	1.11	# compatibility reasons.
72	seemant	1.18	KEYWORDS="~x86"
73	blizzy	1.15
74			# Comprehensive list of any and all USE flags leveraged in the ebuild,
75			# with the exception of any ARCH specific flags, i.e. "ppc", "sparc",
76	vapier	1.27	# "x86" and "alpha". This is a required variable. If the ebuild doesn't
77			# use any USE flags, set to "".
78	vapier	1.39	IUSE="gnome X"
79	blizzy	1.9
80	mr_bones_	1.29	# A space delimited list of portage features to restrict. man 5 ebuild
81			# for details. Usually not needed.
82	genstef	1.37	#RESTRICT="strip"
83	mr_bones_	1.29
84	gbevin	1.3	# Build-time dependencies, such as
85	agriffis	1.24	# ssl? ( >=dev-libs/openssl-0.9.6b )
86			# >=dev-lang/perl-5.6.1-r1
87	gbevin	1.3	# It is advisable to use the >= syntax show above, to reflect what you
88			# had installed on your system when you tested the package. Then
89			# other users hopefully won't be caught without the right version of
90			# a dependency.
91			DEPEND=""
92
93			# Run-time dependencies, same as DEPEND if RDEPEND isn't defined:
94			#RDEPEND=""
95	agenkin	1.7
96			# Source directory; the dir where the sources can be found (automatically
97	mr_bones_	1.26	# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P}
98			# If you don't need to change it, leave the S= line out of the ebuild
99			# to keep it tidy.
100	seemant	1.18	S=${WORKDIR}/${P}
101	achim	1.1
102			src_compile() {
103	gbevin	1.3	# Most open-source packages use GNU autoconf for configuration.
104	vapier	1.33	# The quickest (and preferred) way of running configure is:
105			econf \|\| die "econf failed"
106			#
107			# You could use something similar to the following lines to
108	gbevin	1.3	# configure your package before compilation. The "\|\| die" portion
109			# at the end will stop the build process if the command fails.
110			# You should use this at the end of critical commands in the build
111			# process. (Hint: Most commands are critical, that is, the build
112			# process should abort if they aren't successful.)
113	vapier	1.33	#./configure \
114			# --host=${CHOST} \
115			# --prefix=/usr \
116			# --infodir=/usr/share/info \
117			# --mandir=/usr/share/man \|\| die "./configure failed"
118	gbevin	1.3	# Note the use of --infodir and --mandir, above. This is to make
119			# this package FHS 2.2-compliant. For more information, see
120			# http://www.pathname.com/fhs/
121	blizzy	1.9
122	gbevin	1.3	# emake (previously known as pmake) is a script that calls the
123			# standard GNU make with parallel building options for speedier
124			# builds (especially on SMP systems). Try emake first. It might
125	mr_bones_	1.26	# not work for some packages, because some makefiles have bugs
126			# related to parallelism, in these cases, use emake -j1 to limit
127			# make to a single process. The -j1 is a visual clue to others
128			# that the makefiles have bugs that have been worked around.
129			emake \|\| die "emake failed"
130	achim	1.1	}
131
132	vapier	1.13	src_install() {
133	gbevin	1.3	# You must personally verify that this trick doesn't install
134			# anything outside of DESTDIR; do this by reading and
135	blizzy	1.9	# understanding the install part of the Makefiles.
136	vapier	1.32	# This is the preferred way to install.
137	vapier	1.39	emake DESTDIR="${D}" install \|\| die "emake install failed"
138	genstef	1.38
139			# When you hit a failure with emake, do not just use make. It is
140			# better to fix the Makefiles to allow proper parallelization.
141			# If you fail with that, use "emake -j1", it's still better than make.
142	vapier	1.32
143	gbevin	1.3	# For Makefiles that don't make proper use of DESTDIR, setting
144			# prefix is often an alternative. However if you do this, then
145			# you also need to specify mandir and infodir, since they were
146			# passed to ./configure as absolute paths (overriding the prefix
147			# setting).
148	genstef	1.38	#emake \
149	vapier	1.39	# prefix="${D}"/usr \
150			# mandir="${D}"/usr/share/man \
151			# infodir="${D}"/usr/share/info \
152			# libdir="${D}"/usr/$(get_libdir) \
153	genstef	1.38	# install \|\| die "emake install failed"
154	gbevin	1.3	# Again, verify the Makefiles! We don't want anything falling
155			# outside of ${D}.
156	seemant	1.17
157			# The portage shortcut to the above command is simply:
158			#
159	genstef	1.38	#einstall \|\| die "einstall failed"
160	achim	1.1	}