Paul de Vrieze wrote:
On Saturday 04 March 2006 15:45, Danny van Dyk wrote:
Just to throw in my 2 cents into this discussion: I'm all against
die-ing during the update process. However, i think that stopping
before the update process would be the best solution at hand. I'd like
to propose the addition of a dedicated USE conflict detection to
ebuilds which need it.
Perhaps it would be possible to tell portage to have a
"build-what-you-can" mode, where it tries to build as much as possible
after a compilation failure. At the end it then can report on the
packages that were not compiled.
We've had a bug for this for years, no one has implemented it.
Most of the Portage developers would prefer USE-deps to anything else,
as this is what that is really trying to cover. The only alternative
I'm willing to support at this time is moving the death ( per
Kugelfang's suggestion ) to right after depgraph building. Thus a user
will find out right away that their USE flags conflict and need to be
changed. Even with USE deps, there cases that just aren't resolvable,
they are "unsolveable" and I think coming up with some sort of structure
to inform the user of this is a good idea.
However we have talked about this and the DEPEND syntax doesn't seem to
cut it for showing USE conflicts and dependencies. Certainly right now
the resolver has no metadata whatsoever to work with, so it can't even
tell if a specific set of USE flags conflict or not, if we provide it
with that information it can at least die during depgraph creation
stating what the problem is with the depgraph ( getting closer to having
actaul buildplans... ).
-Alec Warner
--
gentoo-dev@gentoo.org mailing list
