/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.1.1.1 Revision 1.29
1# Copyright 1999-2005 Gentoo Foundation 1# Copyright 1999-2004 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.1.1.1 2005/11/30 09:36:18 chriswhite Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.29 2004/07/25 08:34:01 mr_bones_ 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.
9 9
10# The 'Header' on the third line should just be left alone. When your ebuild 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 11# will be committed to cvs, the details on that line will be automatically
12# generated to contain the correct data. 12# generated to contain the correct data.
13
14# 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:
18inherit 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 13
28# Short one-line description of this package. 14# Short one-line description of this package.
29DESCRIPTION="This is a sample skeleton ebuild file" 15DESCRIPTION="This is a sample skeleton ebuild file"
30 16
31# Homepage, not used by Portage directly but handy for developer reference 17# Homepage, not used by Portage directly but handy for developer reference
61# is in /usr/portage/profiles/. Usually you should just set this to "~x86". 47# is in /usr/portage/profiles/. Usually you should just set this to "~x86".
62# The ~ in front of the architecture indicates that the package is new and 48# The ~ in front of the architecture indicates that the package is new and
63# should be considered unstable until testing proves its stability. Once 49# should be considered unstable until testing proves its stability. Once
64# packages go stable the ~ prefix is removed. So, if you've confirmed that 50# packages go stable the ~ prefix is removed. So, if you've confirmed that
65# your ebuild works on x86 and ppc, you'd specify: KEYWORDS="~x86 ~ppc" 51# your ebuild works on x86 and ppc, you'd specify: KEYWORDS="~x86 ~ppc"
52# For packages that are platform-independent (like Java, PHP or Perl
53# applications) specify all keywords.
66# For binary packages, use -* and then list the archs the bin package 54# For binary packages, use -* and then list the archs the bin package
67# exists for. If the package was for an x86 binary package, then 55# exists for. If the package was for an x86 binary package, then
68# KEYWORDS would be set like this: KEYWORDS="-* x86" 56# KEYWORDS would be set like this: KEYWORDS="-* x86"
69# DO NOT USE KEYWORDS="*". This is deprecated and only for backward 57# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
70# compatibility reasons. 58# compatibility reasons.
98# to keep it tidy. 86# to keep it tidy.
99S=${WORKDIR}/${P} 87S=${WORKDIR}/${P}
100 88
101src_compile() { 89src_compile() {
102 # Most open-source packages use GNU autoconf for configuration. 90 # Most open-source packages use GNU autoconf for configuration.
103 # The quickest (and preferred) way of running configure is:
104 econf || die "econf failed"
105 #
106 # You could use something similar to the following lines to 91 # You should use something similar to the following lines to
107 # configure your package before compilation. The "|| die" portion 92 # configure your package before compilation. The "|| die" portion
108 # at the end will stop the build process if the command fails. 93 # at the end will stop the build process if the command fails.
109 # You should use this at the end of critical commands in the build 94 # You should use this at the end of critical commands in the build
110 # process. (Hint: Most commands are critical, that is, the build 95 # process. (Hint: Most commands are critical, that is, the build
111 # process should abort if they aren't successful.) 96 # process should abort if they aren't successful.)
112 #./configure \ 97 ./configure \
113 # --host=${CHOST} \ 98 --host=${CHOST} \
114 # --prefix=/usr \ 99 --prefix=/usr \
115 # --infodir=/usr/share/info \ 100 --infodir=/usr/share/info \
116 # --mandir=/usr/share/man || die "./configure failed" 101 --mandir=/usr/share/man || die "./configure failed"
117 # Note the use of --infodir and --mandir, above. This is to make 102 # Note the use of --infodir and --mandir, above. This is to make
118 # this package FHS 2.2-compliant. For more information, see 103 # this package FHS 2.2-compliant. For more information, see
119 # http://www.pathname.com/fhs/ 104 # http://www.pathname.com/fhs/
105
106 # Also note that it is cleaner and easier to use econf, which is the
107 # portage shortcut to the above ./configure statement:
108 #
109 # econf || die
110 # Note that econf will die on failure, but please use econf || die
111 # for consistency.
120 112
121 # emake (previously known as pmake) is a script that calls the 113 # emake (previously known as pmake) is a script that calls the
122 # standard GNU make with parallel building options for speedier 114 # standard GNU make with parallel building options for speedier
123 # builds (especially on SMP systems). Try emake first. It might 115 # builds (especially on SMP systems). Try emake first. It might
124 # not work for some packages, because some makefiles have bugs 116 # not work for some packages, because some makefiles have bugs
130 122
131src_install() { 123src_install() {
132 # You must *personally verify* that this trick doesn't install 124 # You must *personally verify* that this trick doesn't install
133 # anything outside of DESTDIR; do this by reading and 125 # anything outside of DESTDIR; do this by reading and
134 # understanding the install part of the Makefiles. 126 # understanding the install part of the Makefiles.
135 # This is the preferred way to install.
136 make DESTDIR=${D} install || die 127 make DESTDIR=${D} install || die
137
138 # For Makefiles that don't make proper use of DESTDIR, setting 128 # For Makefiles that don't make proper use of DESTDIR, setting
139 # prefix is often an alternative. However if you do this, then 129 # prefix is often an alternative. However if you do this, then
140 # you also need to specify mandir and infodir, since they were 130 # you also need to specify mandir and infodir, since they were
141 # passed to ./configure as absolute paths (overriding the prefix 131 # passed to ./configure as absolute paths (overriding the prefix
142 # setting). 132 # setting).
143 #make \ 133 #make \
144 # prefix=${D}/usr \ 134 # prefix=${D}/usr \
145 # mandir=${D}/usr/share/man \ 135 # mandir=${D}/usr/share/man \
146 # infodir=${D}/usr/share/info \ 136 # infodir=${D}/usr/share/info \
147 # libdir=${D}/usr/$(get_libdir) \
148 # install || die 137 # install || die
149 # Again, verify the Makefiles! We don't want anything falling 138 # Again, verify the Makefiles! We don't want anything falling
150 # outside of ${D}. 139 # outside of ${D}.
151 140
152 # The portage shortcut to the above command is simply: 141 # The portage shortcut to the above command is simply:
153 # 142 #
154 #einstall || die 143 #einstall || die
144 # Note that einstall will die on failure, but please use einstall || die
145 # for consistency.
155} 146}

Legend:
Removed from v.1.1.1.1  
changed lines
  Added in v.1.29

  ViewVC Help
Powered by ViewVC 1.1.20