Archives
Archives
| From: | Zac Medico <zmedico@g.o> | ||
|---|---|---|---|
| To: | gentoo-portage-dev@l.g.o | ||
| Subject: | [gentoo-portage-dev] Re: [PATCH] depgraph._resolve: consider unresolved @system atoms fatal (bug 568354) | ||
| Date: | Wed, 16 Dec 2015 03:31:41 | ||
| Message-Id: | 5670DB0F.1040301@gentoo.org | ||
| In Reply to: | [gentoo-portage-dev] [PATCH] depgraph._resolve: consider unresolved @system atoms fatal (bug 568354) by Zac Medico |
||
| 1 | On 12/15/2015 12:46 PM, Zac Medico wrote: |
| 2 | > Since @system atoms are presumably chosen by someone who knows what |
| 3 | > they are doing (usually a gentoo developer), it makes sense to consider |
| 4 | > resolution failures for these atoms as fatal errors. |
| 5 | > |
| 6 | > X-Gentoo-Bug: 568354 |
| 7 | > X-Gentoo-Bug-url: https://bugs.gentoo.org/show_bug.cgi?id=568354 |
| 8 | |
| 9 | Hmm, maybe this should suggest config changes, which could even be |
| 10 | written with --autounmask-write. That would be much friendlier. |
| 11 | -- |
| 12 | Thanks, |
| 13 | Zac |
| Subject | Author |
|---|---|
| Re: [gentoo-portage-dev] Re: [PATCH] depgraph._resolve: consider unresolved @system atoms fatal (bug 568354) | Alexander Berntsen <bernalex@g.o> |