public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@gentoo.org>
To: wolf31o2@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] xorg-x11-6.8.0-r4 needs testers
Date: Thu, 18 Nov 2004 15:39:05 +0000	[thread overview]
Message-ID: <20041118153905.62099aa6@snowdrop.home> (raw)
In-Reply-To: <1100787048.16897.21.camel@cgianelloni.nuvox.net>

[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]

On Thu, 18 Nov 2004 09:10:48 -0500 Chris Gianelloni
<wolf31o2@gentoo.org> wrote:
| On Wed, 2004-11-17 at 15:01 -0800, Donnie Berkholz wrote:
| > Another USE flag that I'm pleased with is "minimal." It disables
| > building all of the sample clients, all of the fonts and many of the
| > drivers. A test install using this was 28MB, compared to 100MB-150MB
| > for a full-featured install.
| 
| Please expound on the "many" of "many of the drivers" for us or point
| us to a location that describes exactly what this removes.  I'm
| curious, because I am currently using "minimal" on LiveCD builds due
| to its impact on vim, but I probably will not want it on xorg-x11 if
| it could possibly break systems or leave out functionality that others
| will want, which means I will have to work around this.

Ick. I'd be inclined to not use minimal vim for livecds, it's *really*
stripped down...  What're the deps pulled in by non-minimal vim that you
don't like?

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, Sparc, Mips)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-11-18 15:39 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 [this message]
2004-11-18 16:21     ` Chris Gianelloni
2004-11-18 17:01       ` Ciaran McCreesh
2004-11-18 19:34         ` Chris Gianelloni
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=20041118153905.62099aa6@snowdrop.home \
    --to=ciaranm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=wolf31o2@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