| 1 |
On Saturday 30 of April 2016 23:16:42 Andreas K. Huettel wrote: |
| 2 |
| Hi all, |
| 3 |
| |
| 4 |
| just as a small reminder, to ease the load on all arch teams: |
| 5 |
| |
| 6 |
| If a stablerequest has the keyword ALLARCHES set, then |
| 7 |
| * the first arch that tests successfully and stabilizes |
| 8 |
| * can and *should* immediately stabilize for all requested arches! |
| 9 |
| |
| 10 |
| Whether this keyword is set on a bug is decision of the package maintainer. |
| 11 |
| |
| 12 |
| For example, Perl team sets ALLARCHES normall for all pure-perl packages |
| 13 |
| (i.e., no compilation / gcc involved). |
| 14 |
| |
| 15 |
| Here's an example how this was used: |
| 16 |
| https://bugs.gentoo.org/show_bug.cgi?id=578408 |
| 17 |
| https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=44c2d31dfc61bb3e2aee370 |
| 18 |
| 9cb5a784b213511fa |
| 19 |
|
| 20 |
Going further, perhaps introducing something along the lines of 'noarch' to |
| 21 |
KEYWORDS syntax would solve the problem in long run? |
| 22 |
Or do we really need to have fine grained control over packages visibility even |
| 23 |
for those that are really processor architecture agnostic? |
| 24 |
|
| 25 |
regards |
| 26 |
MM |
Archives