Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Phil Blundell <philb@gnu.org>,
	and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	Patches
Subject: Re: [RFC] Replacing chrpath with patchelf
Date: Wed, 22 Aug 2012 14:22:21 +0100	[thread overview]
Message-ID: <1345641741.3907.119.camel@ted> (raw)
In-Reply-To: <CAJTo0LYycw59N9tO1i0q5NtTLjUgxwdPRTLQrcZWL7hgaQbmYA@mail.gmail.com>

On Wed, 2012-08-22 at 08:47 +0100, Burton, Ross wrote:
> On 22 August 2012 01:21, Khem Raj <raj.khem@gmail.com> wrote:
> > May be it will be nicer to create one meta
> > package which installs
> > all prerequisites not only chrpath/patchelf and maintain that ourselves
> > this could be nicer since then user only installs
> >
> > apt-get install make-my-host-compile-oe package on ubuntu and similar
> > for others.
> 
> I used to maintain one of these for Debian years ago, and it did help a lot.

These days I'd much rather just ship a tarball with all the bits needed
contained therein. Since we can self-host and we have the nativesdk
infrastructure, this shouldn't be hard and it would work on any distro.

Cheers,

Richard




      reply	other threads:[~2012-08-22 13:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-18  7:17 [RFC] Replacing chrpath with patchelf Khem Raj
2012-08-18 10:31 ` Richard Purdie
2012-08-18 17:15   ` Khem Raj
2012-08-19  1:27     ` Phil Blundell
2012-08-22  0:21       ` Khem Raj
2012-08-22  7:47         ` Burton, Ross
2012-08-22 13:22           ` Richard Purdie [this message]

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=1345641741.3907.119.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=philb@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox