From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Valentin Popa <valentin.popa@intel.com>
Subject: Re: [PATCH] gnomebase: add GNOME_COMPRESS_TYPE variable
Date: Wed, 06 Jun 2012 08:38:01 -0700 [thread overview]
Message-ID: <4FCF7959.3070102@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LY0QBDM5O8t9tvyMxnCnFWBSM3ct7AZZU8W4YZd7Ke-Pw@mail.gmail.com>
On 06/06/2012 03:46 AM, Burton, Ross wrote:
> On 6 June 2012 06:34, Saul Wold<sgw@linux.intel.com> wrote:
>> Upstream Gnome projects are starting to migrate to the .xz compress format,
>> so we need to add this to allow recipes to override the default of .bz2 as
>> the upstreams make the transition.
>
> Considering all future tarballs are going to be .xz, would it make
> sense to default to .xz and fix the recipes where there isn't a .xz?
>
I think until we get a predominant number of the gnome packages updated
there is not much point in doing that as it would require extra recipe
edits. I think if we can do a batch update and then switch the default
that would make more sense. I will leave that up to the new gnome
recipe maintainer Valentin.
Sau!
> Ross
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2012-06-06 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 5:34 [PATCH] gnomebase: add GNOME_COMPRESS_TYPE variable Saul Wold
2012-06-06 10:46 ` Burton, Ross
2012-06-06 15:38 ` Saul Wold [this message]
2012-06-06 17:51 ` Koen Kooi
2012-06-06 23:22 ` Richard Purdie
2012-06-12 9:16 ` Burton, Ross
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=4FCF7959.3070102@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=valentin.popa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox