From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14775 invoked by uid 1002); 28 Jan 2003 14:38:37 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 28451 invoked from network); 28 Jan 2003 14:38:37 -0000 From: Dylan Carlson Reply-To: absinthe@pobox.com To: Marko Mikulicic , Riyad Kalla Date: Tue, 28 Jan 2003 09:32:13 -0500 User-Agent: KMail/1.5 Cc: sh@kde-coder.de, gentoo-dev@gentoo.org References: <000801c2c6d2$e2018f20$d628c480@rskwork> <3E368EC1.8050006@seul.org> In-Reply-To: <3E368EC1.8050006@seul.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200301280932.13923.absinthe@pobox.com> Subject: Re: [gentoo-dev] Split KDE packages? X-Archives-Salt: 2ca06c03-dc87-4b4d-84ca-fb07f2beb091 X-Archives-Hash: 49ccd68701e406f30980068a5c6841b0 On Tuesday 28 January 2003 09:08 am, Marko Mikulicic wrote: > Riyad Kalla wrote: > > Good point... doesn't this require the creation/maintenance of > > hundreds of new ebuilds? > > perhaps using eclass could reduce the body of the ebuild to a standard > template > which can be easly maintained ? KDE currently has it's own set of eclasses. laredo # ls -1 /usr/portage/eclass/kde* /usr/portage/eclass/kde-base.eclass /usr/portage/eclass/kde-pre.eclass /usr/portage/eclass/kde-dist.eclass /usr/portage/eclass/kde-source.eclass /usr/portage/eclass/kde-functions.eclass /usr/portage/eclass/kde.eclass /usr/portage/eclass/kde-i18n.eclass /usr/portage/eclass/kde.org.eclass /usr/portage/eclass/kde-patch.eclass The trick (as the Gentoo devs already know) is getting around the 'configure' time. Take a look at Dan Armak's explanation of the problem in bug # 11123. If you have some specific ideas how those eclasses could be improved to support a granular KDE install, that would be very welcome. My $.02 Caching the workdir will be necessary (via some USE flag like 'kde-cache') unless we pursue something different as proposed in comments #2, #3 of that bug. Dan's correct in saying that caching the configuration stuff is not very elegant. I think the best solution is to hack the eclass to read a variable, which could be set in MAKE.CONF. Something like KDE_PACKAGES="all" or KDE_PACKAGES="kword kspread kmail kwrite" [...etc...] Cheers, Dylan Carlson [absinthe@pobox.com] -- gentoo-dev@gentoo.org mailing list