Since bug #540916 I have the feeling it is not clear to all
developers that we must not rely on implicit eclass inherits.

This has caused problems and breakage in the past and was even
discussed in my recruitment process.

If there are exeptions to this policy, then they have to be
discussed and 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 deletion(-)

-- 
2.2.1


Reply via email to