/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.29 Revision 1.30
1# Copyright 1999-2004 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.29 2004/07/25 08:34:01 mr_bones_ Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.30 2004/08/24 12:14:06 lv 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.
13 27
14# Short one-line description of this package. 28# Short one-line description of this package.
15DESCRIPTION="This is a sample skeleton ebuild file" 29DESCRIPTION="This is a sample skeleton ebuild file"
16 30
17# Homepage, not used by Portage directly but handy for developer reference 31# Homepage, not used by Portage directly but handy for developer reference
132 # setting). 146 # setting).
133 #make \ 147 #make \
134 # prefix=${D}/usr \ 148 # prefix=${D}/usr \
135 # mandir=${D}/usr/share/man \ 149 # mandir=${D}/usr/share/man \
136 # infodir=${D}/usr/share/info \ 150 # infodir=${D}/usr/share/info \
151 # libdir=${D}/usr/$(get_libdir) \
137 # install || die 152 # install || die
138 # Again, verify the Makefiles! We don't want anything falling 153 # Again, verify the Makefiles! We don't want anything falling
139 # outside of ${D}. 154 # outside of ${D}.
140 155
141 # The portage shortcut to the above command is simply: 156 # The portage shortcut to the above command is simply:

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

  ViewVC Help
Powered by ViewVC 1.1.20