From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] xorg-x11-6.8.0-r4 needs testers
Date: Thu, 18 Nov 2004 14:34:30 -0500 [thread overview]
Message-ID: <1100806471.16897.30.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <20041118170125.21d7121c@snowdrop.home>
[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]
On Thu, 2004-11-18 at 17:01 +0000, Ciaran McCreesh wrote:
> Hm, I suspect it's the livecd USE flag on vim-core that's doing most of
> that... Built as:
>
> [ R ] =app-editors/vim-7.0_alpha20040924 -acl -cscope -debug
> -gpm -minimal -mzscheme +ncurses -nls -perl -python -ruby (-selinux)
> -tcltk -vim-with-x 0 kB [1]
>
> which includes proper terminal support, vim comes to about a meg on the
> system I'm on right now. With minimal turned on it comes to just over
> 400KBytes. vim-core built normally is about eleven megs across a
> thousand or so files, built with USE="livecd -nls" it's one meg and ~200
> files (and I could probably nuke a hundred or so of those, if you don't
> mind upsetting people who want to use straaange keymaps).
>
> So, if half a meg (assuming you already have ncurses) isn't too high a
> price for decent terminal (terminfo rather than termcap) support, you
> might not necessarily be best with the minimal USE flag turned on (I'm
> guessing catalyst still doesn't do per-package USE flags easily?).
Actually, it can use package.use just like any normal system.
I'll look into it and see what I can come up with, but it looks like
I'll probably end up running from now on *without* USE=minimal on the
LiveCD. We're already using USE="livecd -nls", so that savings was
definitely appreciated.
--
Chris Gianelloni
Release Engineering - Operational/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-18 19:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 23:01 [gentoo-dev] xorg-x11-6.8.0-r4 needs testers Donnie Berkholz
2004-11-18 0:14 ` Ciaran McCreesh
2004-11-21 14:41 ` Ned Ludd
2004-11-18 14:10 ` Chris Gianelloni
2004-11-18 15:39 ` Ciaran McCreesh
2004-11-18 16:21 ` Chris Gianelloni
2004-11-18 17:01 ` Ciaran McCreesh
2004-11-18 19:34 ` Chris Gianelloni [this message]
2004-11-18 17:08 ` Donnie Berkholz
2004-11-18 17:13 ` Donnie Berkholz
2004-11-18 20:57 ` Ferris McCormick
2004-11-18 18:50 ` Donnie Berkholz
2004-11-18 20:31 ` Chris Gianelloni
2004-11-18 19:58 ` Donnie Berkholz
2004-11-18 21:08 ` Chris Gianelloni
2004-11-18 21:18 ` Chris Gianelloni
2004-11-18 20:26 ` Donnie Berkholz
2004-11-18 21:32 ` Chris Gianelloni
2004-11-18 20:31 ` Joseph Booker
2004-11-18 20:28 ` Donnie Berkholz
2004-11-24 21:45 ` Henrik Brix Andersen
2004-11-19 10:02 ` Paul de Vrieze
2004-11-19 16:44 ` Donnie Berkholz
2004-11-21 23:31 ` Donnie Berkholz
2004-11-18 17:45 ` Michiel de Bruijne
2004-11-18 17:47 ` Donnie Berkholz
2004-11-18 17:58 ` Michiel de Bruijne
2004-11-18 17:58 ` Donnie Berkholz
2004-11-18 18:26 ` Marcus D. Hanwell
2004-11-19 23:13 ` Michiel de Bruijne
2004-11-23 6:50 ` Gábor Farkas
2004-11-23 12:19 ` Jason Stubbs
2004-11-24 6:01 ` [gentoo-dev] " Duncan
2004-11-24 11:41 ` Duncan
2004-11-24 17:00 ` Donnie Berkholz
2004-11-24 12:33 ` [gentoo-dev] " Aaron Walker
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=1100806471.16897.30.camel@cgianelloni.nuvox.net \
--to=wolf31o2@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