| 1 |
On Tue, 28 Feb 2006 10:49:13 +0100 Jakub Moc <jakub@g.o> wrote: |
| 2 |
| No, that's not a policy document, ebuild policy is documented here: |
| 3 |
| http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?style=printable&part=3&chap=1 |
| 4 |
|
| 5 |
No, the whole thing is policy. |
| 6 |
|
| 7 |
| Moreover, the cited howto is wrong, since it will break built_with_use |
| 8 |
| checks |
| 9 |
|
| 10 |
No, that's a separate issue. |
| 11 |
|
| 12 |
| The howto also doesn't apply to cases like |
| 13 |
| recode vs. mysql, because that's a completely different |
| 14 |
| functionality, you can't exactly choose which one is better on behalf |
| 15 |
| of the user. |
| 16 |
|
| 17 |
No, it does apply. |
| 18 |
|
| 19 |
| So, to sum it up - you can't make up for portage's lack of features by |
| 20 |
| inventing a policy that doesn't work. Once again - until portage can |
| 21 |
| handle USE-based dependencies and until portage can handle |
| 22 |
| conflicting use flags, there's nothing that could be done here. |
| 23 |
|
| 24 |
Until Portage can handle conflicting USE flags, one should take the |
| 25 |
policy-mandated solution that has been sufficient for everyone else for |
| 26 |
four years or more. Sure, it's not perfect, but it's a hell of a lot |
| 27 |
better than repeatedly exploding in the user's face midway through an |
| 28 |
install. |
| 29 |
|
| 30 |
-- |
| 31 |
Ciaran McCreesh : Gentoo Developer (Wearer of the shiny hat) |
| 32 |
Mail : ciaranm at gentoo.org |
| 33 |
Web : http://dev.gentoo.org/~ciaranm |
Archives