From: solar <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org, betelgeuse@gentoo.org
Subject: Re: [gentoo-dev] USE="minimal" for kernel sources
Date: Thu, 08 Sep 2005 14:10:05 -0400 [thread overview]
Message-ID: <1126203005.5845.81.camel@alto> (raw)
In-Reply-To: <431C97C4.3070406@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
On Mon, 2005-09-05 at 22:08 +0300, Petteri Räty wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have a couple of old machines I maintain and emerging and unmerging
> kernel sources take a while because there are so many files. Also one
> set of gentoo sources takes about 230MB of disk space. By removing stuff
> not belonging to x86 I was able to succesfully run make with 58MB/230MB
> removed. The stuff I removed:
> arch/* except i386 and x86_64
> include/asm-* expect asm-generic, asm-i386 and asm-x86_64
> So I propose we implement a minimal USE flag in the kernel-2 eclass that
> would make the cleaning I succested before the merging. One problem
> coming from the clean is that make clean does not work and at the moment
> it is run before unmerging, which is of course a good thing. If the
> kernel devs think this is a good idea, I can make an implementation for
> this.
Would something like an unpack.mask/UNPACK_MASK="paths/ wildcards.."
work for you? Perhaps you can simply just take advantage of tar's
--exclude=/-e options in the unpack() function of ebuild.sh when
USERLAND == GNU. Untested patch attached if you want to play
with/perfect the idea. By excluding it from tar you should be able to
save space/cpu/ram all the way around the board while getting the same
end result.
[-- Attachment #2: unpack_mask.patch --]
[-- Type: text/x-patch, Size: 398 bytes --]
--- /usr/bin/ebuild.sh 2005-09-08 13:48:02.000000000 -0400
+++ ebuild.sh 2005-09-08 13:51:13.000000000 -0400
@@ -346,8 +346,9 @@
if [ "$USERLAND" == "BSD" ]; then
tarvars=""
else
- tarvars="--no-same-owner"
- fi
+ tarvars="--no-same-owner"
+ [[ "$UNPACK_MASK" != "" ]] && tarvars="${tarvars} -e \'${UNPACK_MASK}\'"
+ fi
[ -z "$*" ] && die "Nothing passed to the 'unpack' command"
next prev parent reply other threads:[~2005-09-08 18:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 19:08 [gentoo-dev] USE="minimal" for kernel sources Petteri Räty
2005-09-05 20:01 ` Michael Hanselmann
2005-09-05 20:21 ` Petteri Räty
2005-09-08 18:10 ` solar [this message]
2005-09-08 18:17 ` Diego 'Flameeyes' Pettenò
2005-09-08 19:01 ` John Mylchreest
2005-09-08 20:14 ` Jan Kundrát
2005-09-08 20:35 ` John Mylchreest
2005-09-10 15:11 ` Jan Kundrát
2005-09-08 20:36 ` Brian Jackson
2005-09-21 21:28 ` Tom Fredrik Blenning Klaussen
2005-09-21 22:07 ` Alec Warner
2005-09-22 20:28 ` Two-level USE-flag system VAR: " Tom Fredrik Blenning Klaussen
2005-09-22 22:01 ` warnera6
2005-09-23 1:19 ` Jason Stubbs
2005-09-23 6:36 ` [gentoo-dev] Re: Two-level USE-flag system VAR: " Duncan
2005-09-23 7:44 ` Jason Stubbs
2005-09-23 9:22 ` [gentoo-dev] " Duncan
2005-09-23 7:06 ` Two-level USE-flag system VAR: [gentoo-dev] " Thomas de Grenier de Latour
2005-09-08 21:49 ` twofourtysix
2005-09-08 22:14 ` Greg KH
2005-09-08 22:22 ` warnera6
2005-09-09 15:37 ` Petteri Räty
2005-09-09 16:42 ` Alec Warner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1126203005.5845.81.camel@alto \
--to=solar@gentoo.org \
--cc=betelgeuse@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox