[gentoo-commits] proj/devmanual:master commit in: appendices/common-problems/

2022-06-24 Thread Ulrich Müller
commit: 7c8e62980c7e35e115a868a810327c9eb6a471f2
Author: Ulrich Müller  gentoo  org>
AuthorDate: Wed Jun 22 16:22:59 2022 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Fri Jun 24 09:47:42 2022 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=7c8e6298

appendices/common-problems: Remove empty section

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

 appendices/common-problems/text.xml | 11 ---
 1 file changed, 11 deletions(-)

diff --git a/appendices/common-problems/text.xml 
b/appendices/common-problems/text.xml
index 1dc01b8..48fc614 100644
--- a/appendices/common-problems/text.xml
+++ b/appendices/common-problems/text.xml
@@ -149,17 +149,6 @@ you see this notice locally. If you see this notice when 
working with a pure
 
 
 
-
-Handling pkgcheck Messages
-
-
-
-write me
-
-
-
-
-
 
 Handling Access Violations
 



[gentoo-commits] proj/devmanual:master commit in: appendices/common-problems/

2022-06-24 Thread Ulrich Müller
commit: 8b6447f81ecd067d8613d3771e70d17769953b77
Author: Ulrich Müller  gentoo  org>
AuthorDate: Wed Jun 22 16:20:05 2022 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Fri Jun 24 09:47:41 2022 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=8b6447f8

appendices/common-problems: Drop incomprehensible TODO directive

This exists since at least 2005 but nobody has written it.

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

 appendices/common-problems/text.xml | 11 ---
 1 file changed, 11 deletions(-)

diff --git a/appendices/common-problems/text.xml 
b/appendices/common-problems/text.xml
index d124070..1dc01b8 100644
--- a/appendices/common-problems/text.xml
+++ b/appendices/common-problems/text.xml
@@ -145,17 +145,6 @@ you see this notice locally. If you see this notice when 
working with a pure
 emerge sync over rsync setup, it is probably a genuine issue.
 
 
-
-from vapier:
-TEXTREL's ... binary files which contain text relocations ... see
-'prepstrip' for a full description unsafe files ... basically files that
-are setid and writable by Other users i've added the following QA checks to
-Portage HEAD (no idea when they'll hit a release): Insecure RUNPATHs ...
-binary files which have RUNPATH's encoded in them which are in +t
-directories Executable stacks ... binary files whose stack is marked with
-+x ... will bomb on amd64 for example
-
-
 
 
 



[gentoo-commits] proj/devmanual:master commit in: appendices/common-problems/

2021-03-12 Thread Ulrich Müller
commit: 59c460dd367e04cd76eb4dacbca9686e22370d18
Author: Sam James  gentoo  org>
AuthorDate: Fri Mar 12 18:18:30 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Fri Mar 12 20:42:12 2021 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=59c460dd

appendices/common-problems: update eapi7-ver reference

We should refer to them as just built-in helpers now. Note that the linked
page references these anyway, so no need to describe them again.

Closes: https://github.com/gentoo/devmanual/pull/201
Signed-off-by: Sam James  gentoo.org>
Signed-off-by: Ulrich Müller  gentoo.org>

 appendices/common-problems/text.xml | 9 -
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/appendices/common-problems/text.xml 
b/appendices/common-problems/text.xml
index b4fd3ea..a2af22a 100644
--- a/appendices/common-problems/text.xml
+++ b/appendices/common-problems/text.xml
@@ -57,11 +57,10 @@ in use, there are various alternatives:
   
   
 Usually when any of the above are used in global scope, it is to manipulate
-a version or program name string. These should be avoided in favour of
-pure bash constructs. The eapi7-ver eclass is often of use 
here.
-See ,
-man eapi7-ver.eclass and .
+a version or program name string. These should be avoided in favour of pure
+bash constructs. The built-in helpers of EAPI 7 are useful here. See
+
+and .
   
   
 has_version, best_version



[gentoo-commits] proj/devmanual:master commit in: appendices/common-problems/, general-concepts/tree/, ebuild-writing/eapi/, ...

2019-12-26 Thread Ulrich Müller
commit: 143db50760758ca340cc88f41f44955d4d16e1e7
Author: Ulrich Müller  gentoo  org>
AuthorDate: Thu Dec 26 19:27:30 2019 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Thu Dec 26 20:40:27 2019 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=143db507

Remove all p elements below dd.

Where necessary, use multiple dd elements instead.

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

 appendices/common-problems/text.xml |  6 --
 appendices/contributing/text.xml| 31 +--
 appendices/further-reading/text.xml |  6 --
 archs/amd64/text.xml| 12 +++-
 ebuild-writing/eapi/text.xml| 12 ++--
 general-concepts/tree/text.xml  | 25 -
 keywording/text.xml |  8 
 tools-reference/tr/text.xml | 16 +---
 8 files changed, 31 insertions(+), 85 deletions(-)

diff --git a/appendices/common-problems/text.xml 
b/appendices/common-problems/text.xml
index 3af479b..430e74b 100644
--- a/appendices/common-problems/text.xml
+++ b/appendices/common-problems/text.xml
@@ -56,36 +56,30 @@ in use, there are various alternatives:
 sed, awk, grep, egrep, cut etc
   
   
-
 Usually when any of the above are used in global scope, it is to manipulate
 a version or program name string. These should be avoided in favour of
 pure bash constructs. The eapi7-ver eclass is often of use 
here.
 See ,
 man eapi7-ver.eclass and .
-
   
   
 has_version, best_version
   
   
-
 Calls to either of these globally indicates a serious problem. You must 
not
 have metadata varying based upon system-dependent information  see
 . You should rewrite your 
ebuilds
 to correctly use dependencies.
-
   
   
 python, perl etc
   
   
-
 Ebuilds are bash scripts. Offloading anything you don't know how to 
do
 in bash onto another language is not acceptable  if nothing 
else,
 because not all users will always have a full system when ebuilds are
 sourced.
-
   
 
 

diff --git a/appendices/contributing/text.xml b/appendices/contributing/text.xml
index 4b65c41..d17205a 100644
--- a/appendices/contributing/text.xml
+++ b/appendices/contributing/text.xml
@@ -81,34 +81,29 @@ really should first examine the GuideXML guide in a 
reasonable amount of depth.
 Indentation
   
   
-
-  Indent when needed  you should not indent any section flow elements 
such as
-   but do indent tables, lists and definition 
lists.
-  Do not indent text in ordinary paragraph blocks.
-
+Indent when needed  you should not indent any section flow elements
+such as  but do indent tables, lists and
+definition lists. Do not indent text in ordinary paragraph blocks.
   
   
 Code Samples
   
   
-
-  You can use the normal GuideXML tag 
 when you need no 
syntax
-  highlighting. When you need syntax highlighting use the 

-  tag along with a lang attribute  usually you want this to be 
set to
-  ebuild to syntax highlight ebuild code snippets.
-
+You can use the normal GuideXML tag 
 when you need
+no syntax highlighting. When you need syntax highlighting use the
+ tag along with a lang attribute 
+usually you want this to be set to ebuild to syntax highlight ebuild
+code snippets.
   
   
 Hierarchy
   
   
-
-  The whole document is organized as a tree. Each directory can contain one
-  document. Each document can inherit multiple sub-documents using the
-   flag. You must ensure that the self 
tag
-  in each document correctly points to the relative path of the document 
from
-  the root node so that the tree-walking algorithms work correctly.
-
+The whole document is organized as a tree. Each directory can contain
+one document. Each document can inherit multiple sub-documents using the
+ flag. You must ensure that the self
+tag in each document correctly points to the relative path of the document
+from the root node so that the tree-walking algorithms work correctly.
   
 
 

diff --git a/appendices/further-reading/text.xml 
b/appendices/further-reading/text.xml
index d48277c..0a658f6 100644
--- a/appendices/further-reading/text.xml
+++ b/appendices/further-reading/text.xml
@@ -19,12 +19,10 @@ recommendations, not padding designed to make this document 
look important.
 Mastering Regular Expressions
   
   
-
 "Mastering Regular Expressions" by Jeffrey E. F. Friedl (O'Reilly,
 ISBN 0-596-00289-0) is the book on regular expressions. Very 
readable and
 devoid of the usual mathematical jargon that tends to fill up these kinds 
of
 books. http://www.oreilly.com/catalog/regex2/";>Publisher's 
page
-
   
 
 
@@ -40,21 +38,17 @@ recommendations, not padding designed to make this document 
look i

[gentoo-commits] proj/devmanual:master commit in: appendices/common-problems/, eclass-writing/, general-concepts/portage-cache/, ...

2018-10-24 Thread Brian Evans
commit: 1d49e091adefb61f2e5b8dc3a190195651203faa
Author: Brian Evans  gentoo  org>
AuthorDate: Wed Oct 24 17:16:26 2018 +
Commit: Brian Evans  gentoo  org>
CommitDate: Wed Oct 24 17:16:26 2018 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=1d49e091

Remove more versionator references

Signed-off-by: Brian Evans  gentoo.org>

 appendices/common-problems/text.xml | 4 ++--
 ebuild-writing/file-format/text.xml | 4 ++--
 ebuild-writing/variables/text.xml   | 2 +-
 eclass-writing/text.xml | 2 +-
 general-concepts/portage-cache/text.xml | 6 +++---
 xsl/lang.highlight.ebuild.xsl   | 6 ++
 6 files changed, 15 insertions(+), 9 deletions(-)

diff --git a/appendices/common-problems/text.xml 
b/appendices/common-problems/text.xml
index bced1db..992f863 100644
--- a/appendices/common-problems/text.xml
+++ b/appendices/common-problems/text.xml
@@ -57,9 +57,9 @@ in use, there are various alternatives:
 
 Usually when any of the above are used in global scope, it is to manipulate
 a version or program name string. These should be avoided in favour of
-pure bash constructs. The versionator eclass is often of use 
here.
+pure bash constructs. The eapi7-ver eclass is often of use 
here.
 See ,
-man versionator.eclass and man eapi7-ver.eclass and .
 
   

diff --git a/ebuild-writing/file-format/text.xml 
b/ebuild-writing/file-format/text.xml
index f9e6a4f..2c130af 100644
--- a/ebuild-writing/file-format/text.xml
+++ b/ebuild-writing/file-format/text.xml
@@ -130,8 +130,8 @@ is to use  as the version (or as the last 
version component).
 
 
 The
-
-versionator.eclass may be used to manipulate and extract ebuild
+
+eapi7-ver.eclass may be used to manipulate and extract ebuild
 version components.
 
 

diff --git a/ebuild-writing/variables/text.xml 
b/ebuild-writing/variables/text.xml
index f2575ad..98babe4 100644
--- a/ebuild-writing/variables/text.xml
+++ b/ebuild-writing/variables/text.xml
@@ -540,7 +540,7 @@ to read.
 
 Some ebuilds use calls to sed, awk and / or cut to do 
this. This
 must not be done for any new code, and should be fixed to use either
-versionator or bash substitution where possible. Global scope non-bash code is
+eapi7-ver or bash substitution where possible. Global scope non-bash code is
 highly discouraged.
 
 

diff --git a/eclass-writing/text.xml b/eclass-writing/text.xml
index db7d9f1..99824e5 100644
--- a/eclass-writing/text.xml
+++ b/eclass-writing/text.xml
@@ -26,7 +26,7 @@ Roughly speaking, there are three kinds of eclass:
 
   
 Those which provide common functions which are used by many ebuilds (for
-example, eutils, versionator, cvs, 
bash-completion)
+example, eutils, eapi7-ver, cvs, 
bash-completion)
   
   
 Those which provide a basic build system for many similar packages (for

diff --git a/general-concepts/portage-cache/text.xml 
b/general-concepts/portage-cache/text.xml
index f985d56..13dcfae 100644
--- a/general-concepts/portage-cache/text.xml
+++ b/general-concepts/portage-cache/text.xml
@@ -25,14 +25,14 @@ fi
 
 
 
-However, this is legal, since versionator.eclass works upon PV, 
and
+However, this is legal, since eapi7-ver.eclass works upon PV, and
 PV and PN are both static:
 
 
 
-inherit versionator
+inherit eapi7-ver
 
-if [[ $(get_major_version) -ge 7 ]] ; then
+if ver_test -ge 7.0 ; then
IUSE="${IUSE} tcltk mzscheme"
DEPEND="${DEPEND}
tcltk?( dev-lang/tcl )

diff --git a/xsl/lang.highlight.ebuild.xsl b/xsl/lang.highlight.ebuild.xsl
index 4f84b8d..e2b1d72 100644
--- a/xsl/lang.highlight.ebuild.xsl
+++ b/xsl/lang.highlight.ebuild.xsl
@@ -331,6 +331,11 @@

   
 
+  
+  
+   
+  
+
   
   
 
@@ -412,3 +417,4 @@
   
 
 
+



[gentoo-commits] proj/devmanual:master commit in: appendices/common-problems/

2016-05-14 Thread Göktürk Yüksek
commit: e1d909e88aeef35154132d95415d439f09e79adb
Author: Thomas D  whissi  de>
AuthorDate: Wed May 11 01:08:40 2016 +
Commit: Göktürk Yüksek  binghamton  edu>
CommitDate: Sun May 15 01:20:40 2016 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=e1d909e8

appendices/common-problems: Fix anchor link to "Version and Name Formatting 
Issues"

 appendices/common-problems/text.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/appendices/common-problems/text.xml 
b/appendices/common-problems/text.xml
index 2a9a2e7..bced1db 100644
--- a/appendices/common-problems/text.xml
+++ b/appendices/common-problems/text.xml
@@ -58,7 +58,7 @@ in use, there are various alternatives:
 Usually when any of the above are used in global scope, it is to manipulate
 a version or program name string. These should be avoided in favour of
 pure bash constructs. The versionator eclass is often of use 
here.
-See ,
+See ,
 man versionator.eclass and .
 



[gentoo-commits] proj/devmanual:master commit in: appendices/common-problems/

2016-05-04 Thread Göktürk Yüksek
commit: 658d52f0eafaa6c139aa1c6ba5c249afa2e2f4e1
Author: Göktürk Yüksek  binghamton  edu>
AuthorDate: Wed May  4 08:53:44 2016 +
Commit: Göktürk Yüksek  binghamton  edu>
CommitDate: Wed May  4 09:08:20 2016 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=658d52f0

appendices/common-problems: remove the misleading sandbox violation example

In the "Handling Access Violations" section, there is an example of a
build system causing a sandbox violation by attempting to access
HOME. Per PMS, HOME is a predefined read-only environment variable
that points to a temporary location, which doesn't cause any sandbox
violations. Remove the example while keeping the idea of tricking the
build system into using a safer location.

Signed-off-by: Göktürk Yüksek  binghamton.edu>

 appendices/common-problems/text.xml | 30 +-
 1 file changed, 5 insertions(+), 25 deletions(-)

diff --git a/appendices/common-problems/text.xml 
b/appendices/common-problems/text.xml
index b0a7e58..2a9a2e7 100644
--- a/appendices/common-problems/text.xml
+++ b/appendices/common-problems/text.xml
@@ -214,31 +214,11 @@ ebuilds.
 
 
 
-Access violations most commonly occur during the install phase. See
-src_install and 
-for discussion.
-
-
-
-Sometimes problems can also occur with packages attempting to write to
-${HOME}. To get around this, it is usually sufficient to trick the build
-system into using a safer location. For example, the fluxbox menu 
generator
-tries to work in ${HOME}/.fluxbox  to get around this, the 
following is
-used:
-
-
-
-ebegin "Creating a menu file (may take a while)"
-mkdir -p "${T}/home/.fluxbox" || die "mkdir home failed"
-MENUFILENAME="${S}/data/menu" MENUTITLE="Fluxbox ${PV}" \
-CHECKINIT="no. go away." HOME="${T}/home" \
-"${S}"/util/fluxbox-generate_menu -is -ds \
-|| die "menu generation failed"
-eend $?
-
-
-
-In this situation, providing a fake home directory is all that is needed.
+Access violations most commonly occur during the install
+phase. Sometimes it is possible to get around the sandbox violations
+by tricking the build system into using a safer location. See
+src_install and
+ for discussion.