There seems to be some general confusion about specific package SLOTs
and their meaning, since there can be several naming schemes applied
and documentation is either non-existent or is inside the ebuild via
comments.
Because of that it should be part of metadata.xml.
An example use case for media
The following patch tries to address the lack of slot
documentation, since getting the slots of a dependency
right seems like a common problem.
Things that I was particularly not sure about: the 'subslots'
element. Having a sub-element for 'slot' seemed even more
messy, so I tried to make this as
This is particularly useful for people who run alternative
package managers and want to control their configuration.
Github-PR: https://github.com/gentoo/gentoo/pull/69
---
eclass/eutils.eclass | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/eclass/eutils.eclas
---
ebuild-writing/using-eclasses/text.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ebuild-writing/using-eclasses/text.xml
b/ebuild-writing/using-eclasses/text.xml
index 49ec23b..b54f559 100644
--- a/ebuild-writing/using-eclasses/text.xml
+++ b/ebuild-writing/using-ecla
---
ebuild-writing/using-eclasses/text.xml | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/ebuild-writing/using-eclasses/text.xml
b/ebuild-writing/using-eclasses/text.xml
index de9ec7f..49ec23b 100644
--- a/ebuild-writing/using-eclasses/text.xml
+++ b/ebuild-writing/
documented. Otherwise we should expect sane
eclass dependencies from ebuilds without random assumptions.
Julian Ospald (2):
Document policy of not relying on implicit eclass inherits
Fix spelling
ebuild-writing/using-eclasses/text.xml | 10 +-
1 file changed, 9 insertions(+), 1
