Danny van Dyk <[EMAIL PROTECTED]> said: > 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. > > This detection function (for example pkg_prepare()) must be executed for > every > package in the depgraph right after the depgraph has been built and has only > the possibility to either mark the package as 'go' or 'no-go'. In case that > any package has been marked as 'no-go', the whole process stops.
I'd rather see the ebuild marked with some flag to show there are
conflicting use flags that have been resolved, and by adding "--verbose"
or some other flag, you can see what flags are overridden so the user
knows exactly what is going on, and can decide if they like the defaults
the ebuild developer has chosen. I think we should give users the
choice/information to make an informed decision, but I don't think we
should shove a failure into their lap when we can make choices for them
which we believe to be sane.
I'd like less errors/dies during the build/deptree phase and more
warnings/information to be presented so the user could look at it and
make changes, or just accept what we have done for them.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgpuYYiCyv87J.pgp
Description: PGP signature
