All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Joshua Lock : packaged-staging: post-process non-binary files to fix paths packages
Date: Thu, 01 Apr 2010 19:12:00 +0100	[thread overview]
Message-ID: <1270145520.4993.157.camel@rex> (raw)
In-Reply-To: <1270140902.6277.123.camel@trini-m4400>

On Thu, 2010-04-01 at 09:55 -0700, Tom Rini wrote:
> On Thu, 2010-04-01 at 17:34 +0100, Richard Purdie wrote:
> > > There's a lot more than just .la files that get these paths wrong.  If
> > > you use the scan_cmd you set on native/etc for everything you can fix
> > > them all up.
> > 
> > It scans everything for -native packages and just .la files for target
> > packages. I'd argue that for target packages we're better off fixing the
> > problems at source since the real target packages are probably also
> > bust?
> 
> Ah, hmm.  It's possibly just the .la files on the target (which some of
> us would like to see die and I can't argue against), I hadn't really
> bothered to differentiate (and I don't think it's a noticeable time
> diff).  Less logic also brings it closer to working for relocation of
> everything.

But at the cost our target packages are most likely buggy. We accept
the .la files are a problem and there is a solution (libtool sysroot
support) but we're not there yet.

I'd like to see the other problems addressed, not brushed under the
carpet so to speak.

You can trivially make this work on all files in your
local.conf/distro.conf anyway. I'd not like to see that the default.

Cheers,

Richard





  reply	other threads:[~2010-04-01 18:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1NxJrs-0006SS-LZ@melo.openembedded.org>
2010-04-01 16:05 ` [oe-commits] Joshua Lock : packaged-staging: post-process non-binary files to fix paths packages Tom Rini
2010-04-01 16:34   ` Richard Purdie
2010-04-01 16:55     ` Tom Rini
2010-04-01 18:12       ` Richard Purdie [this message]
2010-04-01 19:49         ` Tom Rini

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=1270145520.4993.157.camel@rex \
    --to=rpurdie@rpsys.net \
    --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.