[oe] [oe-commits] org.oe.dev rootfs_ipk: as per OE, policy: remove feed management tools
rpurdie at rpsys.net
Sat Mar 3 20:22:18 CET 2007
On Fri, 2007-03-02 at 10:47 +0100, Koen Kooi wrote:
> As I said, OE still generates 'feeds' in subdirs of deploy/ipk, in contrary of what people
> seem to claim on the mailinglist.
What people are claiming in that the format of deploy/ipk changes from a
single to multiple feeds. This is a behaviour change and people relied
on the old behaviour.
> Using deploy/ipk/ as feed will give you the following problems:
> 1) ipkg doesn't handle upgrades properly if the versions between multiple archtectures
> don't match
An ipkg bug which should be filed somewhere...
> 2) ipkg doesn't handle upgrades proberly when you don't use '-m' (OE does now, but I can
> see people 'optimizing' it and removing '-m' to get more speed)
What does the -m option to ipkg do?
> 3) if you rebuild a package and forget to regenerate Packages your target will freak out
> due to mismatched md5sums
That is a usage problem and one that is easily fixed...
> 4) Packages.filelist can only be generated from scratch, so the former
> deploy/ipk/Packages.filelist was broken
What uses that file?
> That are the easy things, lets look at other problems:
> a) shlib renaming madness. Every now and then something goes wrong with shlib renaming,
> e.g. an app starts shipping an extra util and renaming doesn't work anymore. So you end up
> with 'jpeg_6b.ipk' instead of 'libjpeg6_6b.ipk'. This means you have to edit your Packages
> file to add 'Provides: jpeg' since OE will shlib rename 'RPROVIDES += jpeg' to 'Provides:
This is a problem although it mainly affects long standing distro feeds
rather than people using tmp/deploy as a feed which will probably be
unaffected by such a problem.
> b) Packaging changes without PR bump. If you just blindly rsync, different users will get
> different contents of what appears to be the same package.
Again this is a usage problem. I think people using the feeds directly
will be intelligent enough to be able to deal with this.
> We aren't even mentioning stripping 'Source:' fields to make ipkg consume less RAM and
We could probably improve the OE image feed handling to address that.
> So, knowing all this, do people still want to pretend that a single deploy/ipk feed has no
> problems at all and OE should support it?
Nobody is pretending it has no problems, there are some. People are
saying they're prepared to live with those problems as they need the
> On the feed-management tools:
> The splitting scripts (to split feeds into gpe/ and opie/ and varous other ways) got
> removed and I was told "it's out of scope" by Chris (not to mention the surprise when
> 'bitbake world' mangles deploy/ipk).
That kind of feed splitting is out of scope. It would belong in contrib.
> package-index.bb, however serves a different purpose for me: being able to regenerate
> Packages so I can look at several control files at once,
> instead of using dpkg-deb or ar -x to extract single ones. I'll happily remove it Matthias
> keeps claiming it's a feed management tool.
IMO, it should stay, it is a useful tool.
> Again: the ability to use deploy as a feed is still present, it only moved to subdirectories.
Which changed a behaviour people were relying on.
My view on this is currently that:
* Being able to use tmp/deploy/ipk as a feed is a useful feature
* we should continue to allow that (as developer use only, not for
building real feeds off)
Since a number of people want the older single feed behaviour, I think
we should have some way of allowing that. I understand why people want
the split feed behaviour too and we should allow people to select that
too. Which should be default I don't really care about.
More information about the Openembedded-devel