Gentoo Archives: gentoo-commits

From: "Ulrich Müller" <ulm@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] repo/gentoo:master commit in: /
Date: Sun, 11 Aug 2019 11:04:09
Message-Id: 1565521379.83741fc0363d815511f164a1a071b063fdbbf1ef.ulm@gentoo
1 commit: 83741fc0363d815511f164a1a071b063fdbbf1ef
2 Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
3 AuthorDate: Thu Aug 8 21:49:41 2019 +0000
4 Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
5 CommitDate: Sun Aug 11 11:02:59 2019 +0000
6 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=83741fc0
7
8 skel.ebuild: Use relative paths for directories.
9
10 /usr/portage is no longer the default repository location.
11
12 Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
13
14 skel.ebuild | 25 +++++++++++++------------
15 1 file changed, 13 insertions(+), 12 deletions(-)
16
17 diff --git a/skel.ebuild b/skel.ebuild
18 index 77337142ec3..9c9e6b366eb 100644
19 --- a/skel.ebuild
20 +++ b/skel.ebuild
21 @@ -19,8 +19,8 @@ EAPI=7
22 # without the following line:
23 #inherit autotools
24 #
25 -# eclasses tend to list descriptions of how to use their functions properly.
26 -# take a look at /usr/portage/eclass/ for more examples.
27 +# Eclasses tend to list descriptions of how to use their functions properly.
28 +# Take a look at the eclass/ directory for more examples.
29
30 # Short one-line description of this package.
31 DESCRIPTION="This is a sample skeleton ebuild file"
32 @@ -33,8 +33,8 @@ HOMEPAGE="https://foo.example.org/"
33 SRC_URI="ftp://foo.example.org/${P}.tar.gz"
34
35
36 -# License of the package. This must match the name of file(s) in
37 -# /usr/portage/licenses/. For complex license combination see the developer
38 +# License of the package. This must match the name of file(s) in the
39 +# licenses/ directory. For complex license combination see the developer
40 # docs on gentoo.org for details.
41 LICENSE=""
42
43 @@ -52,14 +52,15 @@ LICENSE=""
44 SLOT="0"
45
46 # Using KEYWORDS, we can record masking information *inside* an ebuild
47 -# instead of relying on an external package.mask file. Right now, you should
48 -# set the KEYWORDS variable for every ebuild so that it contains the names of
49 -# all the architectures with which the ebuild works. All of the official
50 -# architectures can be found in the arch.list file which is in
51 -# /usr/portage/profiles/. Usually you should just set this to "~amd64".
52 -# The ~ in front of the architecture indicates that the package is new and
53 -# should be considered unstable until testing proves its stability. So, if
54 -# you've confirmed that your ebuild works on amd64 and ppc, you'd specify:
55 +# instead of relying on an external package.mask file. Right now, you
56 +# should set the KEYWORDS variable for every ebuild so that it contains
57 +# the names of all the architectures with which the ebuild works.
58 +# All of the official architectures can be found in the arch.list file
59 +# which is in the profiles/ directory. Usually you should just set this
60 +# to "~amd64". The ~ in front of the architecture indicates that the
61 +# package is new and should be considered unstable until testing proves
62 +# its stability. So, if you've confirmed that your ebuild works on
63 +# amd64 and ppc, you'd specify:
64 # KEYWORDS="~amd64 ~ppc"
65 # Once packages go stable, the ~ prefix is removed.
66 # For binary packages, use -* and then list the archs the bin package