| 1 | # Copyright 1999-2005 Gentoo Foundation |
1 | # Copyright 1999-2005 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.34 2005/01/01 05:46:55 dragonheart Exp $ |
3 | # $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.35 2005/12/04 23:51:13 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. |
| … | |
… | |
| 51 | # Note that normal applications should use SLOT="0" if possible, since |
51 | # Note that normal applications should use SLOT="0" if possible, since |
| 52 | # there should only be exactly one version installed at a time. |
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. |
53 | # DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package. |
| 54 | SLOT="0" |
54 | SLOT="0" |
| 55 | |
55 | |
| 56 | # Using KEYWORDS, we can record masking information *inside* an ebuild |
56 | # Using KEYWORDS, we can record masking information *inside* an ebuild |
| 57 | # instead of relying on an external package.mask file. Right now, you |
57 | # instead of relying on an external package.mask file. Right now, you should |
| 58 | # should set the KEYWORDS variable for every ebuild so that it contains |
58 | # set the KEYWORDS variable for every ebuild so that it contains the names of |
| 59 | # the names of all the architectures with which the ebuild works. All of |
59 | # all the architectures with which the ebuild works. All of the official |
| 60 | # the official architectures can be found in the keywords.desc file which |
60 | # architectures can be found in the keywords.desc file which is in |
| 61 | # is in /usr/portage/profiles/. Usually you should just set this to "~x86". |
61 | # /usr/portage/profiles/. Usually you should just set this to "~x86". The ~ |
| 62 | # The ~ in front of the architecture indicates that the package is new and |
62 | # in front of the architecture indicates that the package is new and should be |
| 63 | # should be considered unstable until testing proves its stability. Once |
63 | # considered unstable until testing proves its stability. So, if you've |
| 64 | # packages go stable the ~ prefix is removed. So, if you've confirmed that |
64 | # confirmed that your ebuild works on x86 and ppc, you'd specify: |
| 65 | # your ebuild works on x86 and ppc, you'd specify: KEYWORDS="~x86 ~ppc" |
65 | # KEYWORDS="~x86 ~ppc" |
|
|
66 | # Once packages go stable, the ~ prefix is removed. |
| 66 | # For binary packages, use -* and then list the archs the bin package |
67 | # 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 |
68 | # exists for. If the package was for an x86 binary package, then |
| 68 | # KEYWORDS would be set like this: KEYWORDS="-* x86" |
69 | # KEYWORDS would be set like this: KEYWORDS="-* x86" |
| 69 | # DO NOT USE KEYWORDS="*". This is deprecated and only for backward |
70 | # DO NOT USE KEYWORDS="*". This is deprecated and only for backward |
| 70 | # compatibility reasons. |
71 | # compatibility reasons. |
Parent Directory
| 
Revision Log
| 
Patch