OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: dansawyer on August 19, 2004, 12:43:11 am
-
All,
This is a strategy question relating to releases and feeds. There does not seem to be a consistent practice relating to feeds and the inclusion or support for the non maintained or supported processes. The feeds seem to pick a subset and move them forward. This does not adequitly answer the question of maintenance of the reamainder of the Zaurus package set.
I personally find myself in the bind of needing the features and stability of the later kernels and ROMS yet lacking the availability of the packages not brought forward or upgraded.
What are the alternatives??
What are their drawbacks?
Are we at a point where mix and match are feasable between 1.0.3 and 1.1.3?
If there are specific packages can we move the forward ourselves??
Dan
-
The feeds seem to pick a subset and move them forward. This does not adequitly answer the question of maintenance of the reamainder of the Zaurus package set.
Probably a combination of the releases not being official ones (and therefore not having to contain everything) plus the fact that packages were still being added into OE at the time of release and were therefore not possible to build for the later version.
I personally find myself in the bind of needing the features and stability of the later kernels and ROMS yet lacking the availability of the packages not brought forward or upgraded.
I'm fairly sure that most stuff is backwards compatible, I still use keypebble from 0.9.x.
If there are specific packages can we move the forward ourselves??
On openembedded.org there's a list of unmaintained and non-working packages. See if what you want is on here and become the maintainer. Otherwise it probably does work, but you'll need to build it yourself using OE (until there's a release of course).
Si
-
A strategy is a good thing, it just don't make sense to do it with the currently available system.
OpenZaurus 3.5.1 will be built with gcc 3.4.1 using soft-float. This means the packages will be incompatible to everything else out there, even to 3.3.6-pre1.
After the 3.5.1 release we can start adopting your strategy. In the meantime, there's a lot of room for help. See OzTODO3.5.1 in the OE wiki for a start.
-
Thank you. Where can I find out more about gcc 3.4.1 and soft float. Is that a dynamic binding protocol. Is this the last major lib update? Is there a lib overview?
I am looking at the wiki now. Thanks again
-
On the wiki look at the mailing list archive (and subscribe to it too) and also think about trying IRC for these kind of questions.
Si