* Jose V Beneyto (sepen@crux-arm.nu) wrote:
Hi!
Hey Jose,
I tested the noeabi flavour of RC6 in my HP Jornada 720 and qemu, and both of them worked fine!
yeah, here I have tested the noeabi version in the jornada too, all seem to be working fine, no references to the build enviroment and native builds without problems. About the eabi, same again, tested in the HTC s200 and it's working fine too, I haven't see any problems at the moment.
I think core is now more stable and the best ever, but as we talked many times at irc channel we should add a package manager like pkg-get, so after the installation people could continue completing their systems with hosted packages instead of compiling new ones. This would be helpful for slow devices, or devices with less than 64MB of ram, where compile a port in some cases is not recommended.
Well, I think it's more stable now, but there isn't much feedback from users to know about more problems. The package manager I think it's a good idea (you know) and providing it in the core can be very usefull for some users with old devices (and another option for all) and it isn't so big to disturb the release.
I made some tests with our package collections and it worked as I expected. pkg-get is so fast solving dependencies at client side, but it depends on perl, so we should test all features and options to be sure.
Great, always testing and improving. Good job. Like we told the other day too, we can keep npkg in opt (like you said, it avoids perl dependencie and stays with only bash)
Also pkg-repgen needs a patch (where I'm working on) to avoid getting extra info (dependencies, README files and pre/post install scripts) from the prt-get's stuff installed at host. I think I could have this patch before the end of the week.
I need to deep a bit more with pkg-gen at both sides, client and server. About the patch, don't worry about, there is no hurry. We can keep RC6 there and work about this topic. Take your time.
So with this port I think we can tie up 2.6 development (core), then release RC7 and make a final test. If all goes well RC7 will become our final 2.6 release. At this point it would be good to publish a new tarball for each toolchain, which *could* be used to create more packages.
I've forgotten something?
Well, only a comment about this last paragraph. Like we told along this week, there is no "dig" on the RC and bindutils it's well built (but not commited). We can start a new thread with another topic to talk about this if you think this is better (I think so, I prefer to keep it separately) and see if there are more packages needed (some other interesting tools and may be other of the few ML users can suggest something)
Best regards,
Regards, Victor.
-- Jose V Beneyto | http://sepen.mine.nu/
Learning bit by bit Victor Martinez | http://lokalix.dyndns.org