Oz Feed Management

[Meanie]

I got a few questions regarding the OZ feeds, in particular for the Spitz type machines and related feeds, ie 3.5.4.1

For some packages, there are two versions of each package in the feeds, a arm.ipk and armv5te.ipk
I rather use the armv5te version since I take it those are optimised for the xscale machines. However, the Packages files always contains the arm version of the package. Can I just sed the Packages file and replace the package filenames and replace the checksums?

Also, the 3.5.4 feeds contains more packages than the 3.5.4.1 feeds. I know OZ 3.5.4.1 can use the binaries and packages from both feeds, but since the OZ feeds are quite large, configuring both sets of feeds would only increase the amount of memory used to parse the dependencies which incidentally is the cause of why the GUI package manager crashes because it is running out of memory/resources.

Are the feeds going to remain like they are and updates/upgrades are only going to be added to the upgrades feeds? I am thinking of building an offline feed, ie mirror the feeds to my CF card so I can upgrade and install additional packages whereever I am withhout needing to be constantly connected to the net, ie when I am on a train or plane. This would be good because I can then collapse the files from the 3.5.4 and 3.5.4.1 feeds into the same directory and remove duplicates or outdated packages. Then I just need to regularly synchronise the upgrades feed with my local feed. This would be a perfect solution IMHO if the feed structure does not get reshuffled and only the upgrades feed is updated with new and updated packages.

[Hrw]

Updates/upgrades/addons goes only to feed/upgrades/ directories. I mostly add into 3.5.4.1 upgrade feed - not everytime remember about 3.5.4 one (sorry guys).

3.5.4.1 was built by me, 3.5.4 by Mickeyl and if something is not in 3.5.4.1 (but is in 3.5.4) then I can add it - I had some build problems with some packages (for example E17) so they did not end in feeds.

Packages file contain info for all archs - not only 'arm' ones but also 'armv5te' and machine ones. Ipkg autoselect best one - so on PXA models it will install rather armv5te then arm one.

[Meanie]

Updates/upgrades/addons goes only to feed/upgrades/ directories. I mostly add into 3.5.4.1 upgrade feed - not everytime remember about 3.5.4 one (sorry guys).

3.5.4.1 was built by me, 3.5.4 by Mickeyl and if something is not in 3.5.4.1 (but is in 3.5.4) then I can add it - I had some build problems with some packages (for example E17) so they did not end in feeds.

Packages file contain info for all archs - not only 'arm' ones but also 'armv5te' and machine ones. Ipkg autoselect best one - so on PXA models it will install rather armv5te then arm one.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=139473\"][{POST_SNAPBACK}][/a][/div]

that's good to hear. so I just need to keep the upgrades feed synchronised on my CF card.

there are a few packages missing in the 3.5.4.1 base feed. 3.5.4 base feed has some which are not in 3.5.4.1 base feed nor any other feed. i haven't checked all the packages yet that I need that are missing, but one that comes to mind is the "file" package.

as for the autoselection of architecture with ipkg, it doesn't seem to work. i installed for example abiword and it picked the arm packages instead of the armv5te ones. this is on a spitz.

[koen]

i haven't checked all the packages yet that I need that are missing, but one that comes to mind is the "file" package.

You are correct: http://linuxtogo.org/~koen/OZ/?action=details&pnm=file

as for the autoselection of architecture with ipkg, it doesn't seem to work. i installed for example abiword and it picked the arm packages instead of the armv5te ones. this is on a spitz.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

You are both right: [a href=\"http://linuxtogo.org/~koen/OZ/?action=details&pnm=abiword]http://linuxtogo.org/~koen/OZ/?action=details&pnm=abiword[/url]
If 2.4.5 wouldn't be present, you would have got the armv5te one, but since the arm one is newer...
That being said, the arm one is being built with -mtune=xscale, which is the biggest performance gain. In abiwords case the few extra clz isns sprinkled into a armv5te binary won't do much, maybe 1 or 2 percent, still nice to have, but not anything to lose sleep over.