From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1L6pVY-0006yV-1u for garchives@archives.gentoo.org; Sun, 30 Nov 2008 16:50:56 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F0B20E04F9; Sun, 30 Nov 2008 16:50:53 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id C8CF2E04F9 for ; Sun, 30 Nov 2008 16:50:53 +0000 (UTC) Received: from [192.168.1.33] (unknown [77.246.104.171]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 9A74464279 for ; Sun, 30 Nov 2008 16:50:52 +0000 (UTC) Subject: Re: [gentoo-dev] [RFC] Moving HOMEPAGE out of ebuilds for the future From: Peter Volkov To: gentoo-dev@lists.gentoo.org In-Reply-To: <1228057835.2607.10.camel@mangurrian> References: <1228057835.2607.10.camel@mangurrian> Content-Type: text/plain; charset="UTF-8" Date: Sun, 30 Nov 2008 19:50:17 +0300 Message-Id: <1228063817.25651.147.camel@localhost> 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 X-Mailer: Evolution 2.24.1.1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 9e46f1b9-a138-4691-8bf2-bb4b6056665e X-Archives-Hash: b0984d60b7d0bfa559d6c4e3f32bf74c =D0=92 =D0=92=D1=81=D0=BA, 30/11/2008 =D0=B2 16:10 +0100, Santiago M. Mol= a =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > per-package eclasses [1]. > That way, it would be easy to avoid duplication of not only HOMEPAGE bu= t > also SRC_URI, LICENSE, or any other part of an ebuild. Having per-package eclasses (PPE) just to set common HOMEPAGE is definitely overkill. What other reasons for PPE to exist? If you want to separate common code, then PPE is very dangerous. Take for example ebuilds which share same src_*() function which you had to modify a bit with version bump. To be absolutely sure that you have not broke anything you'll have to check all versions of the package or there are chances that you broke stable tree and have not noticed that. Of course the same stands for eclasses. The difference between PPE and global eclasses is that 1. PPE covers less packages and it'll take longer to notice that error 2. per-package things are changing more rapidly and thus more changes to PPE will be required. All this means that we'll have more breakages. So what are the benefits to overbalance this minuses? --=20 Peter.