Hi all, As part of the 1.1 feature list I suggested a review of the INCOMPATIBLE_LICENSE and COMMERCIAL* package exclusion mechanisms we have within Poky. Below I've outlined my ideas and would

Thanks Liping, this looks good to me. I've merged it into an image-creator branch on contrib I will be collecting image-creator related BitBake patches there for now with the goal of porting them to

Yocto Technical Team, We will be having our regular Technical Team meeting on Tuesday at 8am. If you'd like to join, dial in and agenda are below. Thanks. - Julie Dial in: Tuesday, May 03, 2011,

I just realized another major issue I have with this approach. It doesn't just mean that I _can_ use git fetch to get a specific branch to avoid pulling in a massive pile of objects I don't need, it

Hi, Josh Thanks for your very careful review indeed! I will correct them and resend the patch! Regards, criping

From: Liping Ke <liping.ke@...> Add -t options in bitbake for configuring server type. Signed-off-by: Liping Ke <liping.ke@...> --- bitbake/bin/bitbake | 22 +++++++++++++++++----- 1

From: Liping Ke <liping.ke@...> Add -t options in bitbake for configuring server type. Signed-off-by: Liping Ke <liping.ke@...> Pull URL: git://git.pokylinux.org/poky-contrib.git

Hi Liping, This looks good to me. Two minor typo nits below, once they're fixed I will create a branch on poky-contrib to collect image-creator related patches until we're ready to switch to

Agreed. I don't know what gitolite is capable of. I would really like to be able to create and destroy my own repositories in a central location with other Yocto developers. However, this doesn't

Agreed with the points above. git really is just wrangling a bunch of objects into commit chains and a branch points to a starting point. So I completely agree that all chains don't have to lead

Hi, Can someone please tell me what needs to be done to build qemu-system-mipsel or provide a patch for it? openembedded seems to be able to build something like this, so maybe it would not be too

I think there are three elements to this: a) People do like the logical separation that a repo gives them and find it easiest to think in those terms. b) Most people are used to single relatively

From: Liping Ke <liping.ke@...> Subject: [PATCH 1/1] Resend:[Image-Creator]Make bitbake server type configurable (xmlrpc, none) Add -t options in bitbake for configuring server

From: Liping Ke <liping.ke@...> Add -t options in bitbake for configuring server type. Signed-off-by: Liping Ke <liping.ke@...> Pull URL: git://git.pokylinux.org/poky-contrib.git

most if not all meego repo is on gitorious, why can't Yocto leverage it, at least for now while everything is changing fast? Xianghua <bruce.ashfield@...> wrote:

FYI - If you'd like to view the Yocto schedule at-a-glance, see the file linked to at the top of the Yocto schedule Wiki: https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule. -

This is what I was wondering as well. I had my meta-kernel-dev as a branch on poky-extras and ran into exactly this problem. Either have two clones, or get it into master. Master was the choice,

I'm curious how many people reading this feel this is "basic git". Anyone willing to admit this was the first time they have seen a targeted branch fetch used to avoid a larger download? If everyone

Just to add to this discussion, with gitolite, it should be easy to setup a yocto-contrib repo where each user "owns" the branches under <keyname>/*. This means as ssh keys are added, they'd

Different use case from what I'm seeing as the general concern, however, I would say that if someone has code that doesn't belong in oe-core but it's standalone and useful to the project, then you