public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: evdev broken?
Date: Wed, 20 Jul 2011 18:36:17 +0200	[thread overview]
Message-ID: <3196992.1ruWGEJHkf@nazgul> (raw)
In-Reply-To: <j06nv6$odm$1@dough.gmane.org>

On Wednesday 20 July 2011 14:16:06 Grant Edwards did opine thusly:
> On 2011-07-20, Mick <michaelkintzios@gmail.com> wrote:
> > Every time after you emerge xorg you're meant to remerge its
> > drivers (evdev being one of them).  Usually there is some elog
> > message telling you to run
> > 
> > qfile to find what is need to be reinstalled:
> >   qlist -I -C x11-drivers/
> 
> I've always wondered why, if portage knows that has to be done,
> can't portage just go ahead and do it?

Actually not. Portage doesn't know it has to be done, the ebuild dev 
knows and stuck a literal message in one of the post_() functions.

To do what you mention, the driver would have to depend on xorg, but 
in fact xorg-server depends on the xorg-drivers meta package, which in 
turn depends on the drivers defined in USE.

In theory, one could use PDEPEND I suppose, but I also suspect that 
would cause circular dependencies. The other option is to put an 
emerge call in pkg_postinst() but that would be heavily frowned upon 
as

- it's a highly unusual solution and just an ugly hack
- it wreaks the dep graph that emerge generates
- stuff will get emerged that isn't visible at the beginning
- portage can't definitively tell you before you start that the 
drivers will be remerged


-- 
alan dot mckinnon at gmail dot com



  parent reply	other threads:[~2011-07-20 16:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20  2:50 [gentoo-user] evdev broken? Francisco Ares
2011-07-20  3:05 ` [gentoo-user] " Grant Edwards
2011-07-20  3:10   ` Francisco Ares
2011-07-20  3:38     ` Francisco Ares
2011-07-20  6:05       ` Mick
2011-07-20  6:20         ` Dale
2011-07-20 11:27           ` Francisco Ares
2011-07-20 12:03             ` Alex Schuster
2011-07-20 11:23         ` Francisco Ares
2011-07-20 14:16         ` Grant Edwards
2011-07-20 14:36           ` Mick
2011-07-20 16:36           ` Alan McKinnon [this message]
2011-07-20 19:01             ` Grant Edwards
2011-07-20 16:37           ` Neil Bothwick
2011-07-20 22:34             ` Michael Orlitzky
2011-07-21  8:57               ` Neil Bothwick
2011-07-21 16:13                 ` Michael Orlitzky
2011-07-21 16:44                   ` Neil Bothwick
2011-07-20  3:05 ` [gentoo-user] " Arthur Barlow

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=3196992.1ruWGEJHkf@nazgul \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@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