From: Saul Wold <sgw@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: opkg in svn?
Date: Mon, 18 Nov 2013 07:53:47 -0800 [thread overview]
Message-ID: <528A380B.4020009@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LYapCtQOmaMYtft_wEBsZFZ9NATE1w5cUZrVon_cdzVSQ@mail.gmail.com>
On 11/18/2013 06:21 AM, Burton, Ross wrote:
> On 18 November 2013 12:48, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> On Mon, 2013-11-18 at 12:33 +0000, Burton, Ross wrote:
>>> On 18 November 2013 12:03, Richard Purdie
>>> <richard.purdie@linuxfoundation.org> wrote:
>>>> recipes-sato/puzzles/puzzles_r9765.bb:SRC_URI = "svn://svn.tartarus.org/sgt;module=puzzles;rev=${MOD_PV}"
>>>
>>> Seems like a pretty good reason to ditch puzzles, IMHO.
>>
>> Somehow I knew you'd say that. I still maintain those make a great
>> demo/test app. I'm sure we could just point at a tarball by default for
>> this ;-).
>
> Isn't puzzles the upstream that re-generates tarballs so the checksums
> suddenly change?
>
Yup, that's the one, and they don't keep the older tarballs around
either, a real pain!
Sau!
> Ross
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2013-11-18 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 12:03 opkg in svn? Richard Purdie
2013-11-18 12:33 ` Burton, Ross
2013-11-18 12:48 ` Richard Purdie
2013-11-18 14:21 ` Burton, Ross
2013-11-18 15:53 ` Saul Wold [this message]
2013-11-18 15:10 ` Paul Barker
2013-11-18 16:21 ` Robert Calhoun
2013-11-18 16:50 ` Phil Blundell
2013-11-18 17:27 ` 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=528A380B.4020009@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@intel.com \
/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.