1 |
Nirbheek Chauhan wrote: |
2 |
> On Sun, Nov 8, 2009 at 2:19 AM, Zac Medico <zmedico@g.o> wrote: |
3 |
>> Peter Volkov wrote: |
4 |
>>> Looks like this will not work for all noarch packages. Stardict |
5 |
>>> dictionary itself is noarch, but it RDEPENDS on stardict package which |
6 |
>>> is keyworded only on some archs. So we'll be forced either to keyword |
7 |
>>> stardict on all archs or we need to introduce some new way to work with |
8 |
>>> such situations. |
9 |
>> Keywording stardict on all archs doesn't sound reasonable, so I |
10 |
>> guess we just need to make sure that repoman will allow the noarch |
11 |
>> keyword even though the dependencies aren't keyworded on all |
12 |
>> architectures. |
13 |
> |
14 |
> I think we're going a little far trying to solve a management problem |
15 |
> with technology. If a herd thinks that a particular package can be |
16 |
> safely keyworded (or stabilized) other arches (it just dumps data, is |
17 |
> a simple python module, etc); they should make the call and just do |
18 |
> it. |
19 |
> |
20 |
|
21 |
But we should still have a way to express this in package metadata in |
22 |
some way so it's clear that this is that kind of a package. What zmedico |
23 |
suggested does this nicely but other ways can be used too. |
24 |
|
25 |
Regards, |
26 |
Petteri |