From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Stable source repository
Date: Tue, 22 Jul 2008 15:28:42 -0400 [thread overview]
Message-ID: <488634EA.4080001@balister.org> (raw)
In-Reply-To: <48862F74.70504@palm.com>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
Rich Pixley wrote:
> As a general solution, I think OE needs to support a chain of such
> repositories and I think the OE project itself needs to create and
> maintain one. The only way to be sure that a tarchive will be available
> is if you own and manage the repository yourself. There's precedent for
> this - debian source packages encapsulate the upstream source so that
> the source archive is complete on it's own. This means that the debian
> repositories each contain copies of the upstream tarchives and access to
> the upstream repositories only need to be accessed by debian maintainers
> when creating packaging for a new version.
I suspect that the OE project maintaining a source mirror would be out
of scope for the OE project. However, as noted by Koen, people creating
distributions for OE should maintain source mirrors. (This is needed for
long term GPL compliance).
The point that OE should make it easy to create and maintain source
mirrors is a very good point. What support exist in OE today? (I use
Angstrom, so it just works for me :)
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2008-07-22 19:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 8:11 Stable source repository Esben Haabendal
2008-07-22 8:34 ` Javi Roman
2008-07-22 8:45 ` Leon Woestenberg
2008-07-22 21:07 ` Esben Haabendal
2008-07-30 15:07 ` Leon Woestenberg
2008-07-30 15:30 ` Leon Woestenberg
2008-07-22 11:56 ` Koen Kooi
2008-07-22 21:14 ` Esben Haabendal
2008-07-22 19:05 ` Rich Pixley
2008-07-22 19:28 ` Philip Balister [this message]
2008-07-22 21:17 ` Esben Haabendal
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=488634EA.4080001@balister.org \
--to=philip@balister.org \
--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.