All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: Gstreamer and rpath
Date: Fri, 03 Aug 2007 09:04:56 +0100	[thread overview]
Message-ID: <1186128296.6116.5.camel@localhost.localdomain> (raw)
In-Reply-To: <46B25E0A.7050103@klever.net>

On Fri, 2007-08-03 at 00:43 +0200, Michael Krelin wrote:
> > 
> > I'm actually semi against forcing staging to look like an image. The
> > fact gcc requires this for its sysroot option is a sign that they
> > haven't got this right yet.
> > 
> 
> Why?

Well, why should I put libs in a /usr/lib directory rather that /lib? I
know there are guidelines but guidelines are one thing, forcing layouts
is a different thing.

It was once hoped that by changing variables like libdir, bindir, prefix
in bitbake.conf you could change your system layout. People could then
customise their images that way. I realise there are difficulties with
that in practise as some things are hardcoded and it won't work straight
away at present but if we start using the sysroot option I doubt it will
ever work.

> > With packaged staging we need to decide which way we go, separate
> > staging packages or use the same ones as we use for images.
> > 
> > My personal gut feeling is that separate ones will work better. They
> 
> So is mine, but...
> 
> > also mean we can handle the extra staging files like pkgmaps and perhaps
> > handle multi machine easier.
> > 
> > I think if we try to make image packages fit, we'll end up having to
> > make hack after hack and end up with something less maintainable.
> 
> why?

If staging packages can be different to image ones then we won't mind
customising them. If they have to be the same the only way to adjust for
staging will be to do post install tweaking. That feels like a hack.

Cheers,

Richard




  reply	other threads:[~2007-08-03  8:07 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02  6:10 Gstreamer and rpath Koen Kooi
2007-08-02 10:50 ` Michael Krelin
2007-08-02 11:23   ` Stanislav Brabec
2007-08-02 11:59     ` Michael Krelin
2007-08-02 12:38       ` Stanislav Brabec
2007-08-02 12:40         ` Philip Balister
2007-08-02 12:58           ` Michael Krelin
2007-08-02 13:27           ` Stanislav Brabec
2007-08-02 13:47             ` Koen Kooi
2007-08-02 14:15               ` Stanislav Brabec
2007-08-02 14:20                 ` Koen Kooi
2007-08-02 14:47                   ` Stanislav Brabec
2007-08-02 15:26                     ` Michael Krelin
2007-08-02 15:46                       ` Koen Kooi
2007-08-02 15:52                         ` Michael Krelin
2007-08-02 17:00                           ` Koen Kooi
2007-08-02 17:08                             ` Michael Krelin
2007-08-02 22:16                             ` Richard Purdie
2007-08-02 22:43                               ` Michael Krelin
2007-08-03  8:04                                 ` Richard Purdie [this message]
2007-08-03  9:34                                   ` Michael Krelin
2007-08-05 11:29                                     ` Richard Purdie
2007-08-05 16:27                                       ` Michael Krelin
2007-08-05 20:21                                         ` Stanislav Brabec
2007-08-03  9:21                               ` Stanislav Brabec
2007-08-05 11:32                                 ` Richard Purdie
2007-08-05 20:16                                   ` Stanislav Brabec
2007-08-05 20:27                                   ` Michael Krelin
2007-08-06 10:15                                     ` Stanislav Brabec
2007-08-06 16:28                                       ` Michael Krelin
2007-08-06 17:02                                         ` Stanislav Brabec
2007-08-05  5:55               ` Dr. Michael Lauer
2007-08-05  6:47                 ` Mike (mwester)
2007-08-05  7:17                   ` Dr. Michael Lauer
2007-08-02 12:56         ` Michael Krelin
2007-08-02 13:06           ` Koen Kooi

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=1186128296.6116.5.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.