Bernhard Guillon wrote:
Koen Kooi schrieb:
David McNab wrote:
Hi all,

I notice that in the rootfs images built from an OE tree, the
directory /etc/ipkg points to the central Angstrom feeds.

As it should...

To fix this,

What?!?!?! The intended behaviour ends up being used, so there's
nothing to fix.


The task for a _user_ of getting some package into the official Angstrom
feed is painful and takes a lot of time and effort.

No, it doesn't, you just ask for 'foo' to be included. That works for 99.9% of the packages people want. I am however fussy about machine specific daemons, kernel patches and opie stuff, since people are *very* good at stating they verified things to work when in truth they didn't.

It's very annoying to have people nagging for foo_1.2.bb to get built and packaged and then seeing the same people complain on IRC how some idiot uploaded foo_1.2 (identical to the 'tested' version) to the feeds breaking their systems.

It's because of situations like that that make migrating stuff from .dev to .stable so elaborate. It is also the reason why only autobuilders may upload packages.

Using oe to create the packages and installing them with your own feed
is much more easier. I also prefere to use my own feed.
But as default configuration it is not the right way.

For getting a package into the official Angstrom feed you currently need
to do (as a user):

Get it build with openembedded.devel branch.
- do a patch with mtn
- file a bugreport and include a patch
- find a oe devel to include it into the official devel branch
Get it build with openembedded.stable branch
- use mtn to find out the diff
- apply the diff to the stable branch
- try to build the package
- do this for every depended package which is out of sync with devel branch
- do a patch
- file a bugreport or use the old one
- write to the stable branch mailing list with your patch included
- wait until you find two developer (one of them has to be an
angstrom-core devel) to ack your post
- write mails to devels or keep asking them on irc to comment on patches
because ther are to less developers subscribed or interested on stable
branch to comment on such patches.
- have some luck

Do the same process for the autobuilder skripts.

In my opinion the original post should be included to the Angstrom wiki
so every one can decide to use there own feeds or the Angstrom one.

regards
Bernhard Guillon



_______________________________________________
Angstrom-distro-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users

Reply via email to