From: "Joseph Booker" <joe@neoturbine.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] xorg-x11-6.8.0-r4 needs testers
Date: Thu, 18 Nov 2004 14:31:47 -0600 (CST) [thread overview]
Message-ID: <51467.216.125.51.60.1100809907.squirrel@216.125.51.60> (raw)
In-Reply-To: <1100797713.25786.6.camel@localhost>
On Thu, November 18, 2004 11:08 am, Donnie Berkholz said:
> 1. No fonts. None. Zero. This means X always dies with "Can't find font
> fixed" unless you provide your own. This could potentially be changed if
> I find a way to just build the "misc" fonts.
'essentialfonts' USE flag, on by default
> 2. None of Tad's fancy cursors
'fancycursors', probably on by default
> 3. No clients. This includes xfs, xdm and xkbcomp.
ok, probably somethign that should be in 'minimal'
> 4. Nothing in /usr/share/doc
'doc'
> 5. No Xnest or Xvfb
> 7. For x86 only, remove these video drivers: nsc, glint, tga, s3,
> s3virge, rendition, neomagic, i740, cirrus, tseng, trident, chips, apm,
> ark, cyrix, siliconmotion. I wasn't sure what was safe for other archs
> and didn't want to play around without some more research.
> Of those, the only questionable ones to me are s3, s3virge and
> especially siliconmotion. I could see the latter being popular on
> systems that would otherwise use the "minimal" flag.
How about a VIDEO_DRIVERS enviroment var thats set in make.conf or command
line, that let the ebuild checks for - if its something like 'trident fb
i810', then it builds those, if its not set or empty, then it builds
everything. i think your able to specify alsa drivers in some ebuild that
way
> 8. No man pages
again, the 'doc' USE flag
Wasn't there a GLEP about USE flag grouping? just make '-doc -fancycursors
minimal -fonts' in a USE flag group, when/if that functionality gets into
portage
--
Joseph Booker
joe @ irc.neoturbine.net
jj110888 @ irc.freenode.net
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-11-18 20:32 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
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 [this message]
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=51467.216.125.51.60.1100809907.squirrel@216.125.51.60 \
--to=joe@neoturbine.net \
--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