1 |
Diego 'Flameeyes' Pettenò wrote: |
2 |
> Okay, solar asked me yesterday, and I think this might be the good moment to |
3 |
> start this out. |
4 |
> Right now the x86-fbsd keyword is not being used in the main tree, and the |
5 |
> whole Gentoo/FreeBSD is handled in an overlay, sharing the ~x86 keyword with |
6 |
> standard Gentoo/Linux. |
7 |
> Unfortunately this has a series of drawbacks: |
8 |
> |
9 |
> - we need to package.mask packages that could just not have ~x86-fbsd keyword |
10 |
> at all (because being linux specifics); |
11 |
> - we can see the last working version of a package go away because later |
12 |
> versions are ~x86 and they don't work for us (old flex might have been an |
13 |
> example but that's now fixed; findutils can be another example); |
14 |
> - we cannot make sure that the deptree is satisfied. |
15 |
> |
16 |
> To bring ~x86-fbsd keywording in main tree, we mainly need to move a true |
17 |
> profile in the tree, not a dummy one, mark it as indev and start the |
18 |
> keywording. (I've already cleaned up the default-bsd/fbsd profile so that it |
19 |
> does work with the current base/ profile. |
20 |
> As long as virtual/libc is not in the dependencies, it shouldn't trigger any |
21 |
> kind of problems to leave the sys-freebsd category in the overlay, if we |
22 |
> really need to start needing that, I'll see to make the ebuild quality level. |
23 |
> |
24 |
> It's not going to be a quick thing, as I'm mostly alone with Gentoo/FreeBSD |
25 |
> right now (help is always welcome), but times are mature so that I can |
26 |
> provide a decent experience to users. |
27 |
> |
28 |
> Can anybody name a showstopper to this? |
29 |
> |
30 |
|
31 |
Yes, x86-fbsd is not a 'working'[1] profile keyword. |
32 |
|
33 |
[1]The same reason why ppc-macos has some weird and potentially |
34 |
dangerous profile tricks to keep their systems running. We are looking |
35 |
at adding PROFILE_ARCH, or use.force to the profiles to remedy the |
36 |
situation. Basically portage expands $ARCH into use ( so x86-fbsd has |
37 |
ARCH x86, and would get "x86" in use, which IMHO, isn't that horrible ). |
38 |
However, you also don't get x86-fbsd shoved into USE, so you have to |
39 |
inject it elsewhere, and then users could do something stupid like |
40 |
-x86-fbsd in make.conf, and unset their ARCH flag = bad. |
41 |
|
42 |
PROFILE_ARCH='x86-fbsd' -> would get forcefully injected into USE, OR |
43 |
use.force: x86-fbsd -> a use flag that isn't killed by -*. |
44 |
|
45 |
Whatever the fix is we should be able to make a 2.0.54-r1 release with |
46 |
it, still need to talk to Zac, if anyone has any comments on this, now |
47 |
would be the time ;) |
48 |
|
49 |
-Alec Warner |