| 1 |
On Saturday 04 March 2006 15:45, Danny van Dyk wrote: |
| 2 |
> Just to throw in my 2 cents into this discussion: I'm all against |
| 3 |
> die-ing during the update process. However, i think that stopping |
| 4 |
> before the update process would be the best solution at hand. I'd like |
| 5 |
> to propose the addition of a dedicated USE conflict detection to |
| 6 |
> ebuilds which need it. |
| 7 |
> |
| 8 |
Perhaps it would be possible to tell portage to have a |
| 9 |
"build-what-you-can" mode, where it tries to build as much as possible |
| 10 |
after a compilation failure. At the end it then can report on the |
| 11 |
packages that were not compiled. |
| 12 |
|
| 13 |
> This detection function (for example pkg_prepare()) must be executed |
| 14 |
> for every package in the depgraph right after the depgraph has been |
| 15 |
> built and has only the possibility to either mark the package as 'go' |
| 16 |
> or 'no-go'. In case that any package has been marked as 'no-go', the |
| 17 |
> whole process stops. |
| 18 |
|
| 19 |
And this indeed. |
| 20 |
|
| 21 |
> |
| 22 |
> A possible implementation from the build side could look like this: |
| 23 |
> |
| 24 |
> # the next two functions would be candidates for eutils.eclass |
| 25 |
> emutexuse() { |
| 26 |
> eerror "The following USE flags are mutually exclusive:" |
| 27 |
> eerror "${@}" |
| 28 |
> eerror "Please choose only one of the above and disable the remaining" |
| 29 |
> eerror "USE flags. For additional information about this problem, see" |
| 30 |
> eerror "http://www.gentoo.org/<some place to store add. info about |
| 31 |
> this>" echo |
| 32 |
> } |
| 33 |
> |
| 34 |
|
| 35 |
Add some reference to the package for which they are mutually exclusive. |
| 36 |
|
| 37 |
Paul |
| 38 |
|
| 39 |
-- |
| 40 |
Paul de Vrieze |
| 41 |
Gentoo Developer |
| 42 |
Mail: pauldv@g.o |
| 43 |
Homepage: http://www.devrieze.net |
Archives