From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from corwin.easynet.fr (smarthost160.mail.easynet.fr [212.180.1.160]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j4GBXSBk019473 for ; Mon, 16 May 2005 11:33:28 GMT Received: from easyconnect2121138-64.clients.easynet.fr ([212.11.38.64] helo=eusebe) by corwin.easynet.fr with esmtp (Exim 4.34) id 1DXdqj-0006Uj-Ka for gentoo-dev@lists.gentoo.org; Mon, 16 May 2005 13:33:29 +0200 Date: Mon, 16 May 2005 13:33:15 +0200 From: Thomas de Grenier de Latour To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: i have an idea ! (erescue) Message-ID: <20050516133315.04696000@eusebe> In-Reply-To: References: <200505151718.06501.vapier@gentoo.org> <4287CE08.3080907@gentoo.org> <20050515234110.GA7844@goliath.roninds.net> <200505151812.14013.electronerd@monolith3d.com> <20050516015654.GA7890@goliath.hsd1.oh.comcast.net> Organization: Fasmz X-Mailer: Sylpheed-Claws 1.9.9cvs2 (GTK+ 2.6.7; i686-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 92f04e33-d906-4c4d-be24-0df35540f9d5 X-Archives-Hash: 661dc7ea13eaeab862d1b8d9e9be0ec6 On Mon, 16 May 2005 03:24:21 -0700 Duncan <1i5t5.duncan@cox.net> wrote: > Thus, my suggestion. Why not create a second feature, > toolchain-buildpkg, I'm calling it here for purposes of > developing the suggestion, that's on by default, as contrasted > to the normal buildpkg being off by default. There exists a "buildsyspkg" flag already, which is supposed to build packages for ebuilds that are in the system group. It's probably a bit broken tho (won't catch system packages dependencies that are not explicitly in your profile's system group, and also i don't think the version in portage resolves virtuals). If you're using portage HEAD, you can play with this patch too: http://tdegreni.free.fr/gentoo/portage-20050323--custom_buildpkg.patch It deprecates "buildsyspkg", and instead introduces a new variable for user-defined policy about building binaries. Using it with BUILD_PKGS="*" in make.conf gives a behavior similar to the buildpkg FEATURES flag (keep binaries of everything), and other rules are available too. For instance, i use: BUILD_PKGS="system !sys-kernel kde-base kde-misc \ app-office/openoffice app-office/openoffice-ximian x11-libs/qt" which makes it build binaries for system packages (but the ones from sys-kernel), and also for kde and openoffice stuffs (because they are slow to build so i don't want to revert them from sources if they break). This patch should handle system virtuals fine (although the code organisation is not really nice), but still doesn't track system dependencies. > With such a feature, and with it on by default, another > make.conf parameter would then be useful as well. Call it > binver-depth, and set binver-depth=3 in make.globals. Then, > when three versions of the binpkg are reached, it would delete > the oldest one as it created a new one, thus leaving two > presumably known working backups at all times, even if the > newest version it just created fails. Better to keep that out of emerge imho, there exists some /usr/ portage/packages cleanup scripts already that you can add to your crontab. An example is: https://bugs.gentoo.org/attachment.cgi?id=53397 (it doesn't have your "keep the latest 3 versions" policy tho, but that could be added - I think i see how to do it, only taking care of slotted packaged needs a bit of care). And there are others similar scripts on f.g.o I think. -- TGL. -- gentoo-dev@gentoo.org mailing list