[oe] [oe-commits] org.oe.dev rootfs_ipk: as per OE, policy: remove feed management tools
rpurdie at rpsys.net
Sun Mar 4 11:42:19 CET 2007
On Sun, 2007-03-04 at 01:08 +0100, Matthias Hentges wrote:
> Using a very large ipk feed does indeed work nicely to generate images.
> However, generating Packages can take ages ( and so do image rebuilds
> because of this ). That's about the only problem I see w/ One Giant Feed
We speeded that up quite a bit and there is another speedup planned
which should remove that obstacle. Its been discussed here in the past.
> > My personal experience says multimachine works well and I use if for
> > everything as standard these days. Have you any specific examples or
> > problems? I have been dealing with them as and when I've seen them but I
> > haven't seen any in quite a whiie...
> I wasn't exactly running into real ipkg bugs. I had problems with
> packages using machine-specific stuff for some models ( say all
> sl-c3x00) and hence having their ARCH set as $MACHINE, but not for other
> models ( like collie, poodle ) having their ARCH set as $ARCH.
> It's a packaging bug, not an ipkg bug but annoying in any case ;)
Some packages work like this as a feature, ts-conf now being one of
them. The standard one can be overridden by a machine specific package.
It should just require that the ipkg Architectures are in the right
order. There could also be an issue for ipkg deciding whether it should
use an arch specific package or latest version in a case where packages
that used to be machine specific no longer are. If ipkg can't handle
that, I'd say ipkg needs fixing.
More information about the Openembedded-devel