[gentoo-dev] GlibC

["Mathijs Kwik (-=TRoXX=-)" <troxx@segfault.nl>]

Safe upgrading? :)

I tried 2 things which both fail...
using build-tarball:
changing the bootstrap-file to use glibc-2.2.3-r1 instead of 2.2.3
the build-tarball has 2.2.3-r1 allready installed so installing 2.2.3 would
be stupid(but it's still in the bootstrap-file).

and i also tried installing 2.2.3-r1 on a system with system=tarball
extracted... which also has 2.2.3-r1 in it.


so in both those cases I 'upgrade' a package to itself.
and in both cases it breaks everything on the system...
I don't know what exactly happens on the build-system.
but on the system-system(wow:) I end up having a 0-byte libc-2.2.3.so

so I don't know why this is... it's very easy to regenerate te error (did it
a few times, I thought it was just me:)

so either portage has a buggy, or glibc 2.2.3-r1.ebuild is buggy (because I
never got it to build+installed using portage).

please fix this or help me :)


---


another small thing I don't like (and I'm not the only one, I spoke some
guys on #gentoo who think the same)
the portage-tree is TOOOO big :)
there are things in it like diffs(some quite big) and even the
logo-header-file(almost 2M).
can't we just put all files/* stuff in a separate place on ibiblio/cvs and
put them in ebuild-files? (or let portage check if there are any
diffs/patches/additions)
I mean the portage-tree should just contain enough info to download+build
everything...
having diff's in there for packages that I'm not gonna install anyway seems
useless to me.

It's about 20M now... should be possible to reduce it to 2Mb :)
not because of bandwith, just for clean design.
Some others DO care about bandwith, which I can understand also.


Greetings
/Mathijs