[gentoo-dev] Two requests for ebuild maintainers+writers

[Travis Tilley <lv@gentoo.org>]

I have two requests that will help to make my work incredibly easy. ;)

1) start using $(get_libdir) wherever possible instead of referencing 
lib directly. get_libdir is now part of the eutils eclass and is used by 
gen_usr_ldscript in eutils. so, where previously it had:

cat > ${D}/usr/lib/$1 <<"END_LDSCRIPT"

it now has:

cat > ${D}/usr/$(get_libdir)/$1 <<"END_LDSCRIPT"

The get_libdir function will always return "lib" if using portage 
<2.0.51_pre20 or if CONF_LIBDIR isnt set, so it should be safe to use 
-everywhere-. If CONF_LIBDIR is set, it should return lib32 or lib64, 
depending on what multilib capable arch you are running on. package 
maintainers arent expected to be aware of any issues with using 
lib32/lib64 (well, unless you're an amd64 dev or helping with multilib 
on mips i guess), so feel free to slap any bugs related to lib64/lib32 
onto the arch maintainers. ;)

please mark any lib32/lib64 bugs critical so that they're sure to be 
noticed, even if they're not technically critical. *pokes amd64 devs so 
that they know this was requested and dont downgrade any of those bugs*


2) install and use gcc 3.4 if possible. this isnt a biggie for most 
archs, i'd just like for packages to be tested with gcc 3.4 since I 
havent run into any major problems on amd64 in a while, and would like 
to know what x86 or ppc specifics fail (i expect there to be a small few 
that only fail on these archs). Note that i'm not requesting anyone 
-switch- to gcc 3.4 here, just that they test the packages they maintain 
to see if they fail, and fix them if possible.

a note about c++ apps: if you dont plan on switching to gcc 3.4 
completely, it might not be easy to test any c++ apps. 3.4 includes an 
incompatible libstdc++, and strange bugs pop up or apps fail to compile 
when one dep links to .so.5 (gcc 3.2.3->3.3.x) and another links to 
.so.6 (gcc 3.4.x). they dont -always- pop up, but they -often- do. if 
you keep gcc 3.3 around, some retarded apps still link to .so.5 even 
when compiled using 3.4 unless you move gcc 3.3's libstdc++.so out of 
the way. :/
gcc 3.4 is slotted, but if you switch completely, the suggestion is to 
remove 3.3.x and 3.2.x.

morfic has also been kind enough to provide us with an experimental gcc 
3.4 on x86 profile for those willing to make the switch: 
profiles/default-linux/x86/2004.2/gcc34/


Travis Tilley <lv@gentoo.org>

--
gentoo-dev@gentoo.org mailing list