All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Hans Peter Freyther <holger@moiji-mobile.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] archiver.bbclass: Archive the native builds as well
Date: Sat, 19 Jan 2013 09:44:26 +0100	[thread overview]
Message-ID: <20130119084426.GH15126@xiaoyu.lan> (raw)
In-Reply-To: <50F993A7.30308@linux.intel.com>

On Fri, Jan 18, 2013 at 10:25:43AM -0800, Saul Wold wrote:
> 
> I understand what the issue is here, but I am not sure this is the
> right solution. This will likely bring in way more than is wanted or
> needed for source archiving.
> 
> What's needed from the opkg-utils-native?

IANAL so let me say it is company/personal policy to release more than
would be the minimumm specially to avoid corner cases like we have with
gcc/libgcc.

I think there are some issues..

a.) Missing option to tarball everything. I can prepare a patch for that.

b.) At least libgcc sources not being present.

c.) How can I get back to compliance? I would have to use something like
the old DISTRO_PR after I patched the archiver class and rebuild everything.
How can this be handled today? I have installations in the field that I
want to upgrade, so the PR of each package should increase.

d.) Verify that for the meta-toolchain target the necessary GCC sources
are archived.

cheers
	holger

PS: Re-sent from the right address



  reply	other threads:[~2013-01-19  9:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 14:34 [PATCH] archiver.bbclass: Archive the native builds as well Holger Hans Peter Freyther
2013-01-18 18:24 ` kevin.strasser
2013-01-18 18:35   ` Saul Wold
2013-01-18 18:25 ` Saul Wold
2013-01-19  8:44   ` Holger Hans Peter Freyther [this message]
2013-01-20 12:56     ` Richard Purdie
2013-01-20 15:47       ` Holger Hans Peter Freyther

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=20130119084426.GH15126@xiaoyu.lan \
    --to=holger@moiji-mobile.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.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.