linux.gentoo.dev

`gentoo-dev` `PATCH` skel.ebuild: Use relative paths for directories.


/usr/portage is no longer the default repository location.
Signed-off-by: Ulrich M??ller <ulm_at_gentoo.org>
---
This looks larger than it is, because most of it is caused by
rewrapping of paragraphs. The only text changes are:
"/usr/portage/eclass/" -> "the eclass/ directory"
"/usr/portage/licenses/" -> "the licenses/ directory"
"/usr/portage/profiles/" -> "the profiles/ directory"
skel.ebuild | 25 +++++++++++++------------
1 file changed, 13 insertions(+), 12 deletions(-)
diff --git a/skel.ebuild b/skel.ebuild
index 77337142ec36..9c9e6b366eb9 100644
--- a/skel.ebuild
+++ b/skel.ebuild
_at__at_ -19,8 +19,8 _at__at_ 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"
_at__at_ -33,8 +33,8 _at__at_ 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=""

_at__at_ -52,14 +52,15 _at__at_ 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
--
2.22.0




Written by Ulrich 0 09/08/2019 00:20:01
Check some pics on this site!
25/08/2019 12:58:14