1 |
I've been running multilib-desktop profile for awhile, and the standard |
2 |
multilib profile before it split into desktop and server. However, other |
3 |
than grub, the only stuff I need multilib around for is multilib itself, |
4 |
as I don't do binary only stuff and thus have little use for the 32-bit |
5 |
side. Now the multilib stuff is yet again screwed up (sandbox won't |
6 |
configure, because gcc-config apparently has a screwed up i686-pc-linux- |
7 |
gnu-gcc and an invalid ctarget), and as I'm already tired of spending all |
8 |
that extra time compiling gcc and twice the time compiling glibc, to no |
9 |
end other than to continue multilib support, I decided it's time to dump |
10 |
it! |
11 |
|
12 |
The problem is, I now need both the no-multilib profile and the desktop |
13 |
profile. Is multi-inheritance working yet? Regardless, what's the best |
14 |
way to effectively get both (presumably with no-multilib inheriting from |
15 |
desktop, since no-multilib is clearly the more restricted of the two)? |
16 |
|
17 |
Must I go with no-multilib and fix up the USE flag differences by hand? |
18 |
Other than the obvious 32-bit package masks and gcc/glibc/sandbox/ |
19 |
binutils differences on no-multilib, are there other significant |
20 |
differences in the profiles I need to think about? |
21 |
|
22 |
Maybe it would be better to stay with desktop, and configure the |
23 |
toolchain differences by hand, since I shouldn't need to worry much about |
24 |
the masks, because they're mostly 32-bit binary stuff I'd not be |
25 |
interested in anyway, save for the grub special-case? Do I pretty much |
26 |
just copy the appropriate files from no-multilib to /etc/portage/profile, |
27 |
or is it substantially more complicated than that? |
28 |
|
29 |
What about going forward? Which profile is likely to have the least |
30 |
critical changes, and thus be the easiest to maintain by hand, if that |
31 |
indeed is what I have to do? What sort of tree profile changes am I |
32 |
likely to miss out on? (I suspect it'd be safer to go no-multilib, as |
33 |
changes there are likely to be more critical and necessary to follow, |
34 |
than ones in desktop. I may be wrong.) |
35 |
|
36 |
-- |
37 |
Duncan - List replies preferred. No HTML msgs. |
38 |
"Every nonfree program has a lord, a master -- |
39 |
and if you use the program, he is your master." Richard Stallman |
40 |
|
41 |
-- |
42 |
gentoo-amd64@g.o mailing list |