All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: Using the OpenEmbedded metadata to build Distributions
	<openembedded-devel@openembedded.org>
Subject: Re: 3rd party feeds
Date: Mon, 10 Sep 2007 09:24:27 +0200	[thread overview]
Message-ID: <46E4F12B.9080102@student.utwente.nl> (raw)
In-Reply-To: <46E4E5DB.7050501@gmx.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Schuster schreef:
> Hi,
> suppose I am a 3rd party which develops and maintains packages for a
> distribution (e.g. angstrom).
> 
> how can I provide those packages (say foo) and their dependendencies
> (minus the ones that are already provided by angstrom itself) via a feed.

You ping the angstrom maintainers and they will build that package and put it in the
angstrom feeds.

Angstrom *highly* discourages people to add random feeds from the internet.

regards,

Koen

> To better explain what I mean here is an example. Suppose package foo is
> not part of the Angstrom distribution nor is it in its feeds. foo has a
> dependency on gtk+ (= part of Angstrom) and libbaz (= not part of Angstrom).
> 
> I want to built foo and the feed containing it with a single command:
> 
> bitbake angstrom-plus-feed
> 
> When it finishes I want to have a complete ipk feed which I can copy
> onto a server. It should contain foo, libbaz and not gtk+. Users should
> then add the URL for that feed into their machines and be able to
> install "foo" along with the dependencies. foo and libbaz will be
> fetched from my feed, gtk+ should be fetched from angstrom feed.
> 
> It is clear that I have to built all the angstrom packages on the build
> machine and possibly won't be able to suppress the do_package phase but
> that is not a problem.
> 
> Has OE support for such an approach? If not would you be interested in
> patches allowing it?
> 
> So far I have "emulated" this by using a special PACKAGE_ARCH but that
> is not really a solution.
> 
> Regards
> Robert
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFG5PErMkyGM64RGpERApTjAKCAz9Q3CNNF82oKIxIIXjobT3llNwCff8ts
yerGF07VYo4p6TpuO9dwBpA=
=6235
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2007-09-10  7:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-10  6:36 3rd party feeds Robert Schuster
2007-09-10  6:55 ` Robert Schuster
2007-09-10  7:24 ` Koen Kooi [this message]
2007-09-10  8:00   ` Robert Schuster
2007-09-10 12:32     ` Richard Purdie

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=46E4F12B.9080102@student.utwente.nl \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.