On Sat, 28 Oct 2006, Meino Christian Cramer wrote:
> Hi,
>
> I do an
>
> eix-sync && emerge --pretend --tree --verbose --update --deep world
>
> on a regular basis.
>
> Each time the alsa-headers are offered for update.
>
> If alsa-headers 1.0.13 are installed, alsa-headers 1.0.12 are offered
> for update.
>
> If alsa-headers 1.0.12 are installed, alsa-headers 1.0.13 are offered
> for update.
>
> Seems to be an endless story.
I think what's going on is that alsa-headers, alsa-lib, and alsa-driver
have a sort of incorrect set of dependancies between them. AFAICT,
alsa-driver shouldn't depend on alsa-headers at all, because it seems to
be fine to build ALSA userspace against a newer version of the headers
than your kernel actually supports (which happens automatically and
silently if you're not using alsa-driver; the kernel source has an older
version of ALSA than is the default version of alsa-headers, and no
dependancy on it).
In any case, alsa-lib and alsa-driver don't have dependancies between
them, but each depends on having a matching verison of the headers, and
only alsa-lib permits a newer version of the headers, and alsa-driver is
currently behind, and emerge doesn't back-propagate dependancy
information, but nothing bad actually seems to happen.
-Daniel
*This .sig left intentionally blank*
--
[email protected] mailing list
