| 1 |
Peter Volkov wrote: |
| 2 |
> В Сбт, 07/11/2009 в 12:49 -0800, Zac Medico пишет: |
| 3 |
>> Peter Volkov wrote: |
| 4 |
>>>> We could introduce "noarch" and "~noarch" KEYWORDS, add "noarch" to |
| 5 |
>>>> the default ACCEPT_KEYWORDS setting for all profiles, and instruct |
| 6 |
>>>> unstable users to add "~noarch" to ACCEPT_KEYWORDS. |
| 7 |
>>> Looks like this will not work for all noarch packages. Stardict |
| 8 |
>>> dictionary itself is noarch, but it RDEPENDS on stardict package which |
| 9 |
>>> is keyworded only on some archs. So we'll be forced either to keyword |
| 10 |
>>> stardict on all archs or we need to introduce some new way to work with |
| 11 |
>>> such situations. |
| 12 |
>> Keywording stardict on all archs doesn't sound reasonable, so I |
| 13 |
>> guess we just need to make sure that repoman will allow the noarch |
| 14 |
>> keyword even though the dependencies aren't keyworded on all |
| 15 |
>> architectures. |
| 16 |
> |
| 17 |
> But how will portage handle such situations? Will it allow installation |
| 18 |
> of noarch package and pull in *DEPEND only if possible, or will it |
| 19 |
> prohibit installation of noarch pkgs with unsatisfied deps? The latter |
| 20 |
> will make life harder for tools like eix, I guess. |
| 21 |
|
| 22 |
It should prohibit installation if there are unsatisfied deps. If |
| 23 |
you want "optional" dependencies then that will require a syntax |
| 24 |
extension with an EAPI bump. |
| 25 |
-- |
| 26 |
Thanks, |
| 27 |
Zac |
Archives