public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan@linuxholdings.co.za>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Version conflicts when mixing arch and ~arch
Date: Wed, 11 Oct 2006 12:50:39 +0200	[thread overview]
Message-ID: <200610111250.39630.alan@linuxholdings.co.za> (raw)
In-Reply-To: <200610111119.25506.bo.andresen@zlin.dk>

On Wednesday 11 October 2006 11:19, Bo Ørsted Andresen wrote:
> On Tuesday 10 October 2006 22:37, Alan McKinnon wrote:
> [SNIP]
>
> > emerge -p world had to parse the entire portage tree anyway, it
> > could easily check for versioning conflicts while doing it and
> > display a message to the user, much like blockers do currently. I
> > get it that portage likely can't suggest resolutions but it would
> > be nice to see in one display that evas and pygtk requires mutually
> > exclusive versions of cairo.
> >
> > Can portage do this? Is it something useful that warrants a feature
> > request? Or am I missing an option in the man page even though I've
> > read it >30 times? :-)
>
> After bug #147766 [1] and bug #16365 [2] have been resolved portage
> should detect this. That means that the latest stable portage still
> won't detect it but latest ~arch portage should...
>
> [1] https://bugs.gentoo.org/147766
> [2] https://bugs.gentoo.org/16365

That's good news. My notebook runs ~x86, meaning I can test the latest 
portage there and keyword portage on the desktop if everything seems 
fine.

Thanks for the info

alan

-- 
gentoo-user@gentoo.org mailing list



      reply	other threads:[~2006-10-11 10:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 20:37 [gentoo-user] Version conflicts when mixing arch and ~arch Alan McKinnon
2006-10-11  9:19 ` Bo Ørsted Andresen
2006-10-11 10:50   ` Alan McKinnon [this message]

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=200610111250.39630.alan@linuxholdings.co.za \
    --to=alan@linuxholdings.co.za \
    --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