[gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/, ebuild-maintenance/maintenance-tasks/

["Ulrich Müller" <ulm@gentoo.org>]

commit:     07452705c2b149c0510d64c72dc9e474bd0f8363
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Mon Jun 17 19:51:59 2019 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Mon Jun 17 19:51:59 2019 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=07452705

Avoid absolute (and outdated) /usr/portage path.

Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 ebuild-maintenance/maintenance-tasks/text.xml | 9 ++++-----
 ebuild-writing/common-mistakes/text.xml       | 4 ++--
 2 files changed, 6 insertions(+), 7 deletions(-)

diff --git a/ebuild-maintenance/maintenance-tasks/text.xml b/ebuild-maintenance/maintenance-tasks/text.xml
index a434fb5..06634b8 100644
--- a/ebuild-maintenance/maintenance-tasks/text.xml
+++ b/ebuild-maintenance/maintenance-tasks/text.xml
@@ -34,11 +34,10 @@ select all possible fields, then submit the query. For you lazy people, click
 In general, the Gentoo repository should only be used for storing
 <path>.ebuild</path> files, as well as any relatively small companion
 files, such as patches or sample configuration files. These types of
-files should be placed in the
-<path>/usr/portage/mycat/mypkg/files</path> directory to keep the main
-<path>mycat/mypkg</path> directory uncluttered. Exceptions to this
-rule are for larger patch files (we recommend this for patches above
-20KB) which should be distributed as tarballs via the
+files should be placed in the <path>mycat/mypkg/files</path> directory
+to keep the main <path>mycat/mypkg</path> directory uncluttered.
+Exceptions to this rule are for larger patch files (we recommend this
+for patches above 20KB) which should be distributed as tarballs via the
 <uri link="::general-concepts/mirrors/#suitable-download-hosts">Gentoo
 mirror system</uri> so that people do not waste excessive amounts of
 bandwidth and hard drive space. Also, you should not add binary

diff --git a/ebuild-writing/common-mistakes/text.xml b/ebuild-writing/common-mistakes/text.xml
index 2842531..869676e 100644
--- a/ebuild-writing/common-mistakes/text.xml
+++ b/ebuild-writing/common-mistakes/text.xml
@@ -300,14 +300,14 @@ Another common mistake users make when submitting ebuilds is supplying an
 invalid license. For example, <c>GPL</c> is not a valid license. You need to
 specify <c>GPL-1</c> or <c>GPL-2</c>. Same with <c>LGPL</c>. Make sure the
 license you use in the <c>LICENSE</c> field is something that exists in
-<path>/usr/portage/licenses</path>. As a tip, check the <path>COPYING</path>
+the <path>licenses</path> directory. As a tip, check the <path>COPYING</path>
 in a source tarball for the license. If a package does not specify it
 uses <c>GPL-1</c> or <c>GPL-2</c>, it is very likely it uses <c>GPL-2</c>.
 </p>
 
 <p>
 If the license for the package you submit is unique and not in
-<path>/usr/portage/licenses/</path>, then you must submit the new license in a
+<path>licenses/</path>, then you must submit the new license in a
 separate file.
 </p>