Hello, Johannes! Johannes Winkelmann schrieb:
On Tue, May 29, 2007 at 15:55:14 +0200, bisco wrote:
Jesse Kokkarinen ha scritto: [...]
A few of the crux "ports" you refer to are already linked [1]. They are unofficial and do not fall under the responsibility of crux itself.
*smile* Can somebody please explain what the "responsibility of crux" is? I got the impression that it's the user's responsibility only, to get things right. ;-)
[...]
the _real_ question is: why are these unofficial projects yet?
Probably because these projects are developed completely independent from the CRUX project.
Yes. I am wondering about that. I just see no good reason to develop them independently. From my embedded ppc system's point of view it look pretty obvious: Most of the core ports are 100% identical on ix86 and ppc. Only a few ports are obviously platform dependent: binutils, glibc, gcc, (libstc++-compat if necessary). Some ports need minor compatibility patches or an additional ./configure parameter which are already in my ports repository: coreutils, unzip. fdisk/lilo/grub gets replaced by mac-fdisk/yaboot/ofboot So, I would estimate a maximum of 5% of the ports differ from my platform to the ix86 CRUX-2.3. The differences are really trivial, once you've them in. I see no point why we shouldn't share the other 95% of port maintenance. Well, I just override the official ports with mine.
What do you think would be the benefits of merging the CRUX PPC projects into the CRUX (crux.nu) project
I don't think it's necessary to merge both projects. I just want that they point/link together.
, especially for the CRUX x86 side?
Because then you don't talk x86 only anymore.
I ask this especially since I can't remember seeing patches/generic fixes from the PPC developers sent to crux-devel.
Thats simply because there are hardly patches necessary. unzip needs a make linux_noasm to avoid x86 instructions. coreutils needs a patch for uname to get the non x86 platform names right. Well, that's it. The other patches I pushed recently came from my ppc system but they are valid for all platforms (when we move on to gcc-4.2.0).
One of the things I'd like to stress here is that previously, the main problem was communication. If you want to be considered as future team members, you'll somehow need to get into a position to make the crux x86 devs want to work together with you, and trust you. That won't happen overnight, and not as long as you think (and publically express) the problems are just with "the others".
My primary intention of this thread was to have a link right in the "Introduction" at crux.nu at least to the PPC site, to give the puplic an idea, that CRUX is something more than i686-optimized. (I know the Link section...) CRUX is IMHO very attractive for the embedded market, because it's very slim and easily customizable. Over here, it's PowerPC, but it doesn't really matter a lot, what CPU it is, as long as it's CRUX! 8-) Regards, -- Clemens Koller __________________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Straße 45/1 Linhof Werksgelände D-81379 München Tel.089-741518-50 Fax 089-741518-19 http://www.anagramm-technology.com