1 |
Hi, |
2 |
|
3 |
I've just marked the profile 'default/bsd/fbsd/amd64/9.0' as 'stable' |
4 |
in profiles.desc. I've been careful not to keyword anything with broken |
5 |
deps, and its now forbidden. It is the first g/fbsd profile marked as |
6 |
such. |
7 |
|
8 |
Consequences for devs: broken deps are not allowed anymore; people are, |
9 |
like for standard arches, expected to drop keywords and fill a |
10 |
rekeywording bug. |
11 |
|
12 |
Rationale: |
13 |
- x86-fbsd has been a 'dev' profile for so long that the |
14 |
majority of the packages have broken deps, meaning moving it to a |
15 |
'stable' profile is almost impossible. I do not want to repeat this |
16 |
error for amd64-fbsd |
17 |
- people usually do not run repoman -d, and as such, it is common to |
18 |
get (core or not) packages that are uninstallable on g/fbsd. This |
19 |
wont happen anymore and will make devs and users happier :=) |
20 |
|
21 |
cons: there's no stable amd64-fbsd keyword, i suppose that if we want |
22 |
some day to stabilize it, it'll be hard with a 'stable' profile, but we |
23 |
can temporarily switch it back to 'dev' while doing it, and without |
24 |
preventing broken deps it'll be almost impossible to do this anyway. |
25 |
|
26 |
Regards, |
27 |
|
28 |
A. |