/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.50 Revision 1.56
1# Copyright 1999-2008 Gentoo Foundation 1# Copyright 1999-2011 Gentoo Foundation
2# Distributed under the terms of the GNU General Public License v2 2# Distributed under the terms of the GNU General Public License v2
3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.50 2008/03/14 02:22:02 betelgeuse Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.56 2011/04/08 01:30:14 vapier Exp $
4 4
5# NOTE: The comments in this file are for instruction and documentation. 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 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 7# remember to remove them before submitting or committing your ebuild. That
8# doesn't mean you can't add your own comments though. 8# doesn't mean you can't add your own comments though.
13 13
14# The EAPI variable tells the ebuild format in use. 14# The EAPI variable tells the ebuild format in use.
15# Defaults to 0 if not specified. The current PMS draft contains details on 15# Defaults to 0 if not specified. The current PMS draft contains details on
16# a proposed EAPI=0 definition but is not finalized yet. 16# a proposed EAPI=0 definition but is not finalized yet.
17# Eclasses will test for this variable if they need to use EAPI > 0 features. 17# Eclasses will test for this variable if they need to use EAPI > 0 features.
18# Ebuilds should not define EAPI > 0 unless they absolutely need to use
19# features added in that version.
20#EAPI=0 18#EAPI=0
21 19
22# inherit lists eclasses to inherit functions from. Almost all ebuilds should 20# inherit lists eclasses to inherit functions from. Almost all ebuilds should
23# inherit eutils, as a large amount of important functionality has been 21# inherit eutils, as a large amount of important functionality has been
24# moved there. For example, the $(get_libdir) mentioned below wont work 22# moved there. For example, the epatch call mentioned below wont work
25# without the following line: 23# without the following line:
26inherit eutils 24inherit eutils
27# A well-used example of an eclass function that needs eutils is epatch. If 25# A well-used example of an eclass function that needs eutils is epatch. If
28# your source needs patches applied, it's suggested to put your patch in the 26# your source needs patches applied, it's suggested to put your patch in the
29# 'files' directory and use: 27# 'files' directory and use:
30# 28#
31# epatch ${FILESDIR}/patch-name-here 29# epatch "${FILESDIR}"/patch-name-here
32# 30#
33# eclasses tend to list descriptions of how to use their functions properly. 31# eclasses tend to list descriptions of how to use their functions properly.
34# take a look at /usr/portage/eclasses/ for more examples. 32# take a look at /usr/portage/eclasses/ for more examples.
35 33
36# Short one-line description of this package. 34# Short one-line description of this package.
63 61
64# Using KEYWORDS, we can record masking information *inside* an ebuild 62# Using KEYWORDS, we can record masking information *inside* an ebuild
65# instead of relying on an external package.mask file. Right now, you should 63# instead of relying on an external package.mask file. Right now, you should
66# set the KEYWORDS variable for every ebuild so that it contains the names of 64# set the KEYWORDS variable for every ebuild so that it contains the names of
67# all the architectures with which the ebuild works. All of the official 65# all the architectures with which the ebuild works. All of the official
68# architectures can be found in the keywords.desc file which is in 66# architectures can be found in the arch.list file which is in
69# /usr/portage/profiles/. Usually you should just set this to "~x86". The ~ 67# /usr/portage/profiles/. Usually you should just set this to "~x86". The ~
70# in front of the architecture indicates that the package is new and should be 68# in front of the architecture indicates that the package is new and should be
71# considered unstable until testing proves its stability. So, if you've 69# considered unstable until testing proves its stability. So, if you've
72# confirmed that your ebuild works on x86 and ppc, you'd specify: 70# confirmed that your ebuild works on x86 and ppc, you'd specify:
73# KEYWORDS="~x86 ~ppc" 71# KEYWORDS="~x86 ~ppc"
94# >=dev-lang/perl-5.6.1-r1 92# >=dev-lang/perl-5.6.1-r1
95# It is advisable to use the >= syntax show above, to reflect what you 93# It is advisable to use the >= syntax show above, to reflect what you
96# had installed on your system when you tested the package. Then 94# had installed on your system when you tested the package. Then
97# other users hopefully won't be caught without the right version of 95# other users hopefully won't be caught without the right version of
98# a dependency. 96# a dependency.
99DEPEND="" 97#DEPEND=""
100 98
101# Run-time dependencies. Must be defined to whatever this depends on to run. 99# Run-time dependencies. Must be defined to whatever this depends on to run.
102# The below is valid if the same run-time depends are required to compile. 100# The below is valid if the same run-time depends are required to compile.
103RDEPEND="${DEPEND}" 101RDEPEND="${DEPEND}"
104 102
106# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P} 104# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P}
107# If you don't need to change it, leave the S= line out of the ebuild 105# If you don't need to change it, leave the S= line out of the ebuild
108# to keep it tidy. 106# to keep it tidy.
109#S="${WORKDIR}/${P}" 107#S="${WORKDIR}/${P}"
110 108
109
110# The following src_compile function is implemented as default by portage, so
111# you only need to call it, if you need a different behaviour.
111src_compile() { 112#src_compile() {
112 # Most open-source packages use GNU autoconf for configuration. 113 # Most open-source packages use GNU autoconf for configuration.
113 # The quickest (and preferred) way of running configure is: 114 # The default, quickest (and preferred) way of running configure is:
114 econf || die "econf failed" 115 #econf
115 # 116 #
116 # You could use something similar to the following lines to 117 # You could use something similar to the following lines to
117 # configure your package before compilation. The "|| die" portion 118 # configure your package before compilation. The "|| die" portion
118 # at the end will stop the build process if the command fails. 119 # at the end will stop the build process if the command fails.
119 # You should use this at the end of critical commands in the build 120 # You should use this at the end of critical commands in the build
133 # builds (especially on SMP systems). Try emake first. It might 134 # builds (especially on SMP systems). Try emake first. It might
134 # not work for some packages, because some makefiles have bugs 135 # not work for some packages, because some makefiles have bugs
135 # related to parallelism, in these cases, use emake -j1 to limit 136 # related to parallelism, in these cases, use emake -j1 to limit
136 # make to a single process. The -j1 is a visual clue to others 137 # make to a single process. The -j1 is a visual clue to others
137 # that the makefiles have bugs that have been worked around. 138 # that the makefiles have bugs that have been worked around.
139
138 emake || die "emake failed" 140 #emake || die "emake failed"
139} 141#}
140 142
141src_install() { 143src_install() {
142 # You must *personally verify* that this trick doesn't install 144 # You must *personally verify* that this trick doesn't install
143 # anything outside of DESTDIR; do this by reading and 145 # anything outside of DESTDIR; do this by reading and
144 # understanding the install part of the Makefiles. 146 # understanding the install part of the Makefiles.

Legend:
Removed from v.1.50  
changed lines
  Added in v.1.56

  ViewVC Help
Powered by ViewVC 1.1.20