diff options
author | V3n3RiX <venerix@redcorelinux.org> | 2019-08-18 18:16:17 +0100 |
---|---|---|
committer | V3n3RiX <venerix@redcorelinux.org> | 2019-08-18 18:16:17 +0100 |
commit | fc637fb28da700da71ec2064d65ca5a7a31b9c6c (patch) | |
tree | 326613a08f25851c388715e205576a2e7d25dc4f /skel.ebuild | |
parent | b24bd25253fe093f722ab576d29fdc41d04cb1ee (diff) |
gentoo resync : 18.08.2019
Diffstat (limited to 'skel.ebuild')
-rw-r--r-- | skel.ebuild | 25 |
1 files changed, 13 insertions, 12 deletions
diff --git a/skel.ebuild b/skel.ebuild index 77337142ec36..9c9e6b366eb9 100644 --- a/skel.ebuild +++ b/skel.ebuild @@ -19,8 +19,8 @@ EAPI=7 # without the following line: #inherit autotools # -# eclasses tend to list descriptions of how to use their functions properly. -# take a look at /usr/portage/eclass/ for more examples. +# Eclasses tend to list descriptions of how to use their functions properly. +# Take a look at the eclass/ directory for more examples. # Short one-line description of this package. DESCRIPTION="This is a sample skeleton ebuild file" @@ -33,8 +33,8 @@ HOMEPAGE="https://foo.example.org/" SRC_URI="ftp://foo.example.org/${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 +# License of the package. This must match the name of file(s) in the +# licenses/ directory. For complex license combination see the developer # docs on gentoo.org for details. LICENSE="" @@ -52,14 +52,15 @@ LICENSE="" 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 arch.list file which is in -# /usr/portage/profiles/. Usually you should just set this to "~amd64". -# 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 amd64 and ppc, you'd specify: +# 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 arch.list file +# which is in the profiles/ directory. Usually you should just set this +# to "~amd64". 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 +# amd64 and ppc, you'd specify: # KEYWORDS="~amd64 ~ppc" # Once packages go stable, the ~ prefix is removed. # For binary packages, use -* and then list the archs the bin package |