public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Some new xorg ebuilds
Date: Wed, 20 Apr 2005 03:39:53 -0700	[thread overview]
Message-ID: <pan.2005.04.20.10.39.49.722905@cox.net> (raw)
In-Reply-To: 1113912662.13564.5.camel@sponge.fungus

Henrik Brix Andersen posted <1113912662.13564.5.camel@sponge.fungus>,
excerpted below,  on Tue, 19 Apr 2005 14:11:02 +0200:

> On Tue, 2005-04-19 at 11:15 +0200, Sebastian Bergmann wrote:
>>  Is there a list of "major" changes for X.Org 6.9.0 (or whatever
>>  release 6.8.99.* is leading to) somewhere? How far do you estimate
>>  this release to be away?
> 
> http://xorg.freedesktop.org/wiki/#head-7f9963a87b2eb461fc821f70af0cecbb33788ba8

Very useful information, particularly the modularization proposal as
linked from there.

After reading The Modularization Proposal, and noting from the front page
linked above that it has apparently been adopted, I've still some
questions, mostly re Gentoo's implementation thereof.

The big one, how are we handling the modularization.  It has been obvious
for some time from Donnie's comments that he's taking Gentoo's xorg toward
modularized, but that leaves open the question of how exactly it's going
to be done.

Is the modularization going to be handled much as the KDE splits were
handled?  That is, as with KDE having both the multilithic (multi- due to
still having multiple category packages) and split ebuilds available for
3.4, will xorg 6.9 (current imake monolithic build system, according to
the link above) and 7.0 (modularized autotools based build) exist at the
same time, with xorg-7.0 being effectively a meta-ebuild of the multiple
individual packages, similar to kdebase-meta, or will we switch to
modularized immediately (or...)?

Once we go 7.0/modularized, what will it look like in terms of the
versioning of the individual components?  As with KDE, are they going to
say in sync with the main upstream release, with individual new package
versions getting -rN revision numbers, or are we going to have individual
package versions with no relation to the xorg release, save for the
xorg-7.x meta-ebuild having deps on >= whatever the highest component
ebuild version for that particular package was at that point?

More to the immediate point, are the 6.8.99 snapshots going to be
modularized more or less as they become available upstream (if it's not
already happening, I haven't yet checked), or should we (I) expect a 6.99
modularized meta-package set of snapshots to become available at some
point?

Finally, are all the Gentoo local system location changes now (as of
6.8.2-r1 or r2?) complete, or are there still more coming?  IOW, are we
testers now testing /only/ new xorg code, or are we still testing local
system location changes as well?

...

Also, one more question, local xorg configuration related.  I'm currently
running dual VGA screen xinerama on a single dual-output Radeon AGP card.
I'd /love/ to be able to run dual cards, an AGP and a PCI, letting me run
up to four monitors, but have tried several different hardware
arrangements and save for the success I had some time ago with a GForce2
and NVidia's proprietary drivers (totalling three monitors on two cards),
I've not gotten it working. Is there an official list of dual card
supporting xorg drivers, anywhere, and/or perhaps an xorg-user list
dealing with such things?  I did notice the note about r128 now supporting
dual-card layout in the changes since 6.8.2 doc linked from above, which
again reminded me that I'd like to get it working.  2 x 2048x1536, 21"
monitors, stacked for 2048x3072, is nice, but a 2x2 layout for 4096x3072
total display area would DEFINITELY be nicer!  =8^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-04-20 10:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19  8:00 [gentoo-dev] Some new xorg ebuilds Donnie Berkholz
2005-04-19  9:15 ` Sebastian Bergmann
2005-04-19 12:11   ` Henrik Brix Andersen
2005-04-20 10:39     ` Duncan [this message]
2005-04-20 18:25       ` [gentoo-dev] " Donnie Berkholz
2005-04-21  9:42         ` [gentoo-dev] " Duncan
2005-04-19 19:46 ` [gentoo-dev] " Paul de Vrieze
2005-04-19 19:56   ` Stefan Schweizer
2005-04-19 21:11   ` Donnie Berkholz
2005-04-21 13:19     ` Paul de Vrieze
2005-04-21 18:03       ` Donnie Berkholz
2005-04-20  1:27 ` Daniel Goller
2005-04-20  2:58   ` Donnie Berkholz
2005-05-04 10:54     ` [gentoo-dev] " Duncan
2005-05-04 19:03       ` Donnie Berkholz
2005-05-05 10:11         ` [gentoo-dev] " Duncan
2005-05-05 15:20           ` Donnie Berkholz
2005-05-06  2:27             ` [gentoo-dev] " Duncan
2005-04-20  5:49 ` [gentoo-dev] " Donnie Berkholz
2005-04-20  5:52   ` Donnie Berkholz
2005-04-20  9:10     ` Marcus D. Hanwell
2005-05-22 21:14 ` Beber [Gentoo]
2005-05-23  5:08   ` Donnie Berkholz

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=pan.2005.04.20.10.39.49.722905@cox.net \
    --to=1i5t5.duncan@cox.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