public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas de Grenier de Latour <degrenier@easyconnect.fr>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] xorg-server 1.0.99/1.1 ABI break
Date: Mon, 17 Apr 2006 22:31:29 +0200	[thread overview]
Message-ID: <20060417223129.7a3ed206@eusebe> (raw)
In-Reply-To: <4443C024.1030405@gentoo.org>

On Mon, 17 Apr 2006 09:19:48 -0700,
Donnie Berkholz <spyderous@gentoo.org> wrote:

> Simon Stelling wrote:
> > Donnie Berkholz wrote:
> >> We are working to ensure the dependencies work as smoothly as
> >> possible, but I expect there will be some issues since it's
> >> difficult to require updates to all these optional drivers
> >> following an update to the server.
> > 
> > wouldn't !< atoms solve that problem?
> 
> The drivers cannot be upgraded until a newer server is installed. So
> technically, this would allow things to work by forcing people to
> unmerge all their drivers before upgrading, then remerge the new
> versions. That's not a very desirable solution either, but do you
> think it's the best one?
> 

What about a big PDEPEND in xorg-server-1.1 ebuild, with a bunch of
"video_cards_foobar? ( >=x11-drivers/xf86-video-foobar-NewVersion )"?
That should be enough to force a smooth update of the video drivers
after the server. And, the RDEPEND on video drivers could be removed
from the xorg-x11 meta-ebuild, to avoid redundancy.

Sure, it doesn't help users who have manually emerged some drivers
without listing them all in $VIDEO_CARDS: they will still be able to
update their server and keep some old broken drivers behind. But
hopefully, they won't be so numerous (much less numerous than those who
would be annoyed by some "!<..." block imho).

--
TGL.
-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-04-17 20:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-17  5:18 [gentoo-dev] xorg-server 1.0.99/1.1 ABI break Donnie Berkholz
2006-04-17  9:57 ` Simon Stelling
2006-04-17 16:19   ` Donnie Berkholz
2006-04-17 19:02     ` Alec Warner
2006-04-17 20:05       ` Donnie Berkholz
2006-04-17 20:26         ` Olivier Crête
2006-04-17 20:34           ` Diego 'Flameeyes' Pettenò
2006-04-17 20:34           ` Donnie Berkholz
2006-04-17 20:48             ` Alec Warner
2006-04-17 20:31     ` Thomas de Grenier de Latour [this message]
2006-04-17 20:43       ` Donnie Berkholz
2006-04-17 20:53         ` Alec Warner
2006-04-18  0:12         ` Thomas de Grenier de Latour
2006-04-18  0:48           ` Donnie Berkholz
2006-04-18  1:26             ` Thomas de Grenier de Latour
2006-04-21 13:49 ` Sebastian Bergmann
2006-04-21 16:10   ` 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=20060417223129.7a3ed206@eusebe \
    --to=degrenier@easyconnect.fr \
    --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