All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaap de Jong <jaap.dejong@nedap.com>
To: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: foreign repository
Date: Mon, 26 Mar 2012 14:05:36 +0200	[thread overview]
Message-ID: <4F705B90.2000408@nedap.com> (raw)
In-Reply-To: <CAFZPMoYNvc4XFdSy9_xH-CYb8R1MOR8-7XsWU0medQFBnWTs8g@mail.gmail.com>

Thanks!

It was never my intention to create new recipes for all the packages 
that are in this foreign repository.
I would have to update every 2 weeks or so to keep in sync with that 
repository.
Don't want that!

I only want to install the package that is in that repository and its 
dependencies.

This is what I did.
Added the foreign repository in: angstrom-feed-configs.bbappend
So with 'opkg update' it is read.
Created an empty 'placeholder' recipe for the package to include.
When I bitbake my image this empty package is included in the rootfs.
Now i only have to 'opkg update/upgrade' to get the actual packages in.
This is by far the easiest solution (I think...)

Thanks again!
Jaap


On 03/26/2012 12:31 PM, Sergey Lapin wrote:
> On Mon, Mar 26, 2012 at 1:57 PM, Jaap de Jong<jaap.dejong@nedap.com>  wrote:
>> Anyone?
>> Any idea?
> You can read OE wiki regarding overlays/layers.
> Also, you can use Koen's Angstrom scripts for no-brains configuration process.
> Also, bitbake manual and OE existing layers are your friends.
>
> S.
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>



      reply	other threads:[~2012-03-26 12:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 13:27 foreign repository Jaap de Jong
2012-03-26  9:57 ` Jaap de Jong
2012-03-26 10:31   ` Sergey Lapin
2012-03-26 12:05     ` Jaap de Jong [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F705B90.2000408@nedap.com \
    --to=jaap.dejong@nedap.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.