public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] xorg-server 1.0.99/1.1 ABI break
Date: Mon, 17 Apr 2006 16:48:00 -0400	[thread overview]
Message-ID: <4443FF00.1090109@gentoo.org> (raw)
In-Reply-To: <4443FBF3.4000608@gentoo.org>

Donnie Berkholz wrote:
> Olivier Crête wrote:
> 
>> On Mon, 2006-17-04 at 13:05 -0700, Donnie Berkholz wrote:
>>
>>> Alec Warner wrote:
>>>
>>>> Well the semantics of the blocker is that the new driver won't work 
>>>> with the old server; is that true?  Or just the old drivers won't 
>>>> work with the new server?
>>>
>>> New server requires new drivers. Old server requires old drivers. 
>>> There is no valid combination of new and old.
>>
>>
>> Then you should probably has new drivers block old servers and new
>> servers block old drivers...
> 
> 
> OK, let's think about the results of this.
> 
> New drivers block old servers:
>     Rather, why wouldn't new drivers depend on a new server? This makes 
> sense and is already what we're doing.
> 
> New servers block old drivers:
>     This will require people to uninstall all their drivers to upgrade 
> their server. It will not automatically reinstall them in the 'emerge -u 
> xorg-server' case, but it _should_ reinstall them in the 'emerge -u 
> world' case _if_ they're using the xorg-x11 metabuild.
> 

I'll take TGL's suggestion, New server PDEPENDS on new drivers.

New drivers need new server, old drivers won't work with new server, 
doesn't touch the old driver ebuilds at all; I don't particularly see a 
down side ;)

> I'm not sure whether portage does a --deep by default now, but I think 
> that's what is necessary for correct behavior in the 'emerge -u world' 
> case.
It doesn't.
> 
> Thanks,
> Donnie

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-04-17 20:51 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 [this message]
2006-04-17 20:31     ` Thomas de Grenier de Latour
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=4443FF00.1090109@gentoo.org \
    --to=antarus@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