* Jose V Beneyto (sepen@crux-arm.nu) wrote:
Hello guys,
[...]
Well, I was wondering about to create a new branch for the toolchain called 2.6-uclibc or to create a new repository called toolchain-uclibc. I prefer the last one, but what do you think is the best?
I like more the branch way but I'm not sure about side effects (for example having more than one toolchain at the same time). In this sense we keep all related toolchain work in the same git repository, only making diffs between branches. In other hand, I can think in a repository grow, having all that info in the same repository and making branches, in this sense, splitting in a nother repository could be good.
Note that in the past, there was a version of CRUX called uCRUX by the simple fact of being built against uclibc, so that's for what I want to create a new repository instead of a branch. After that, you could send patches against this toolchain's stuff, or if you want, we can give you enough permissions to work directly on the git repository.
It can be great if Luka wants to work directly in a repository, giving us the possibility to follow his work and work with him.
Also note that we should make a little organization in order to release more files and packages. A proposal could be:
http://crux-arm.nu/releases/2.6/ crux-arm-rootfs-2.6-noeabi.tar.bz2 crux-arm-rootfs-2.6.tar.bz2 crux-arm-uclibc-rootfs-2.6-noeabi.tar.bz2 crux-arm-uclibc-rootfs-2.6.tar.bz2 toolchain-uclibc-2.6-noeabi.tar.bz2 toolchain-uclibc-2.6.tar.bz2
and locations for stored packages:
http://crux-arm.nu/pkg/2.6/ http://crux-arm.nu/pkg/2.6-noeabi/ http://crux-arm.nu/pkg/uclibc-2.6/ http://crux-arm.nu/pkg/uclibc-2.6-noeabi/
Comments?
I like the names and the organization structure.
Regards,
Regards, Victor. --- Learning bit by bit Victor Martinez | http://lokalix.dyndns.org