1 |
On Thu, 16 Jan 2014, Sergey Popov wrote: |
2 |
>> 3. Also, another interesting question has come up in this thread, that of |
3 |
>> non-binary packages. Should we give maintainers the option of |
4 |
>> stabilizing them on all arch's themselves? |
5 |
> 3. If code is interpreted rather then compiled, it does not matter that |
6 |
> it is properly ported on minor arches. I knew dozens of examples with |
7 |
> Perl and Python packages(not sure about Ruby, but Hans said that it |
8 |
> happens with it too). So, i would not treat such packages differently. |
9 |
OK, let's be conservative. Python and Perl scripts may break on some |
10 |
arches (I'd say it's a rare exception, perhaps 1%, but still). But what |
11 |
about |
12 |
|
13 |
dev-java/java-sdk-docs |
14 |
dev-db/postgresql-docs |
15 |
sys-kernel/linux-docs |
16 |
dev-dotnet/gtk-sharp-docs |
17 |
app-xemacs/general-docs |
18 |
dev-util/kdevelop-php-docs |
19 |
dev-util/gnome-devel-docs |
20 |
app-vim/phpdocs |
21 |
gnome-extra/gnome-user-docs |
22 |
gnome-extra/gnome-getting-started-docs |
23 |
dev-php/smarty-docs |
24 |
dev-python/python-docs |
25 |
dev-python/cheetah-docs |
26 |
app-doc/php-docs |
27 |
app-doc/root-docs |
28 |
app-doc/geant-docs |
29 |
app-doc/blas-docs |
30 |
app-doc/lapack-docs |
31 |
app-doc/gnucash-docs |
32 |
app-office/abiword-docs |
33 |
dev-lisp/hyperspec |
34 |
sys-apps/man-pages[-*] |
35 |
|
36 |
and maybe others? They contain no scripts which can possibly break. I'd |
37 |
say they should be keyworded on all arches as soon as they are keyworded |
38 |
on the first arch; the same goes for stabilization. I'd include also |
39 |
packages containing only TeX/LaTeX code - TeX behaves identically on all |
40 |
arches, this was and is its main strength. Also, probably, |
41 |
python/perl/ruby interpreted scripts *which don't load extra libraries* |
42 |
work identically on all arches not in 99% of cases but in 99.99% (0.01% is |
43 |
for cases when the interpreter is broken on a given arch). |
44 |
|
45 |
Andrey |