From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id B0EDE138A2F for ; Mon, 18 Aug 2014 12:30:53 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B1316E0B17; Mon, 18 Aug 2014 12:30:47 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id CA0BAE0AE6 for ; Mon, 18 Aug 2014 12:30:46 +0000 (UTC) Received: from 127.0.0.1 (unknown [92.51.245.84]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: hasufell) by smtp.gentoo.org (Postfix) with ESMTPSA id 3C77633FF41 for ; Mon, 18 Aug 2014 12:30:43 +0000 (UTC) Message-ID: <53F1F1EB.6030601@gentoo.org> Date: Mon, 18 Aug 2014 12:30:35 +0000 From: hasufell Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] rfc: calling all eclass phase functions by default References: <20140816215428.GA6773@linux1> <53F1BF3C.9060902@gentoo.org> <53F1EBE7.6090700@gentoo.org> <53F1EF49.9030503@gentoo.org> In-Reply-To: <53F1EF49.9030503@gentoo.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: daa71ee2-12cf-45ee-8a55-633b9efef86b X-Archives-Hash: ade30d645ba35084b7af61e7be177cae Sergey Popov: > 18.08.2014 16:04, hasufell пишет: >>> You have my strong opposition on such change as well. It will turn >>> ebuilds into unreadable and undpredictable mess, please do not do that >>> >> >> They are already fairly unreadable and unpredictable. >> > > For you - maybe. But not for me. > > I am NOT talking about hacks like putting additional *.as files through > echo(hello Boost ebuild) or doing something crazy with subshells. > > But most of the eclass and ebuilds are readable quite simple if you read > devmanual, PMS and have a brain. > > Of course, there are sometimes non-trivial stuff that is hard to read. > > But majority of ebuilds and eclasses are fine to understand and predict. > > So, without examples from you, this discussion will lead to nowhere, so, > please let's stop it. > >From my time as a sunrise dev I strongly disagree. People have problems with understanding the mess, including actual programmers. They have enough technical understanding, but not the time or motivation to go through all those funny pitfalls which are NOT properly documented in devmanual. The most popular example is what we are talking about right now: indirect inheritance for example via games.eclass which inherits base.eclass but does not export src_unpack so stuff like unpacker.eclass and git-2.eclass will likely just do nothing if you inherit them before games.eclass (which is required by games herd policy)... uhm. I doubt you would have guessed this one if you saw the plain ebuild. I know the pitfall, so I see it just from looking at the inherit line. But it is far from being obvious.