From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25550 invoked by uid 1002); 6 Dec 2003 22:50:56 -0600 Mailing-List: contact gentoo-portage-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail Reply-To: gentoo-portage-dev@gentoo.org X-BeenThere: gentoo-portage-dev@gentoo.org Received: (qmail 31717 invoked from network); 6 Dec 2003 22:50:56 -0600 From: Ray Russell Reese III To: gentoo-portage-dev@gentoo.org In-Reply-To: <200312061839.56139.george@gentoo.org> References: <004901c3bc63$9c47ef10$9601a8c0@jason01> <200312061839.56139.george@gentoo.org> Content-Type: text/plain Message-Id: <1070772654.2768.10.camel@milton.zerotech.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sat, 06 Dec 2003 23:50:54 -0500 Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page X-Archives-Salt: 3b1fb17a-6729-45b6-8f8d-56bc61aa5fb5 X-Archives-Hash: 6ebfa3f40bc5096f1139c714f8dec947 Wouldn't it be wise then to allow for multiple ebuild formats through plug-ins? Like you say, a considerable amount of ebuilds need nothing more than to run configure, make, and make install. Then there are those ebuilds that are a few hundred lines (or gasp more) of bash script that would benefit from something more structured. What that something is I honestly don't know. But at least with the plug-able ebuild format, we could retain compatibility with the current ebuilds, and slowly phase them into something more appropriate. Just my $0.02. - Ray Russell Reese III [ freenode:anti ] On Sat, 2003-12-06 at 21:39, George Shapovalov wrote: > On Saturday 06 December 2003 17:44, Jason Stubbs wrote: > > It's not getting ahead of things! That's a requirement that's not > > covered yet. "Package definition should be powerful but simple with a > > small learning curve" or something to that effect. > > Hm, isn't it a bit too late to change ebuild format, with us sitting on 7000+ > ebuilds? The only reasonable way to do so is to make it structurally > compatible and create a converter tool. Even then this is a major endeavor > that would require a very good reason (nothing short of deadly limitations of > the present format, which I woudn't say is the case). Furthermore, this would > require wide publicity and even votes if we do not want to alienate users, as > this is the change that definitely will affect them (take a look at number of > new ebuild submissions ;)). > > But then I don't really see the problem with present format. bash involvment > is really necessary only during the pkg_* and src_* steps, when a lot of > other stuff is going to happen anyway, so this is hardly a bottleneck. To get > definitions of various vars and dependency information out is trivial and can > be done in anything. That bash is involved in this step at present is > unfortunate, but there were reasons for it and it definitely may be undone > even for the present portage. > > George > > > > -- > gentoo-portage-dev@gentoo.org mailing list > -- gentoo-portage-dev@gentoo.org mailing list