All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@openembedded.org
Subject: Re: Package Maintenance
Date: Wed, 25 Mar 2009 18:54:32 -0500	[thread overview]
Message-ID: <49CAC438.2020907@dls.net> (raw)
In-Reply-To: <49CAAFDC.3070004@bolloretelecom.eu>

Jeremy Lainé wrote:
>>> Empty TMPDIR is only once case we should test for, I've seen many times that
>>> a 'populated' TMPDIR creates bugs, e.g. midori picking up libhildon to
>>> mention a recent one. So 'always build from empty TMPDIR' will leave serious
>>> and harder to trackdown bugs unnoticed.
>> Test with unpopulataed TMPDIR and test with maximal populated TMPDIR ?
> 
> Speaking of populated TMPDIR, is there a notion of conflicts for staging? If two packages
> want to put the same file into staging, will we barf an error or silently ignore it?

It silently ignores it.

As a current example, unless distros have taken special care with libusb
and libusb1, they will suffer from exactly this problem, with the
library that is staged determined by which recipe is built most recently.

-Mike (mwester)



  reply	other threads:[~2009-03-25 23:56 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17 19:18 Package Maintenance Chris Larson
2009-03-17 19:25 ` Koen Kooi
2009-03-17 19:32   ` Chris Larson
2009-03-17 19:43   ` Frans Meulenbroeks
2009-03-23 20:35 ` Chris Larson
2009-03-24  9:06   ` Richard Purdie
2009-03-24 15:08     ` Chris Larson
2009-03-24 18:36       ` Frans Meulenbroeks
2009-03-24 18:54         ` Tom Rini
2009-03-24 18:55         ` Chris Larson
2009-03-24 19:14           ` Koen Kooi
2009-03-24 19:24             ` Chris Larson
2009-03-24 19:50               ` Tom Rini
2009-03-24 19:59                 ` Chris Larson
2009-03-24 18:56         ` Junqian Gordon Xu
2009-03-24 19:05           ` Chris Larson
2009-03-24 19:19             ` Junqian Gordon Xu
2009-03-24 19:29               ` Philip Balister
2009-03-24 19:51                 ` Tim Ellis
2009-03-24 20:01                   ` Chris Larson
2009-03-24 20:16                     ` Koen Kooi
2009-03-24 20:30                     ` Lon Lentz
2009-03-24 20:44                       ` Junqian Gordon Xu
2009-03-25  8:51                         ` Frans Meulenbroeks
2009-03-25 11:03                           ` Koen Kooi
2009-03-25 13:36                             ` Richard Purdie
2009-03-25 14:16                               ` Holger Schurig
2009-03-25 14:40                                 ` Richard Purdie
2009-03-25 15:32                                 ` Holger Schurig
2009-03-25 14:26                               ` Otavio Salvador
2009-03-25 16:05                             ` Mike (mwester)
2009-03-25 16:20                               ` Koen Kooi
2009-03-25 18:03                                 ` Jeremy Lainé
2009-03-25 18:22                                   ` Koen Kooi
2009-03-25 18:13                                 ` Mike (mwester)
2009-03-25 22:07                                 ` Frans Meulenbroeks
2009-03-25 22:27                                   ` Jeremy Lainé
2009-03-25 23:54                                     ` Mike (mwester) [this message]
2009-03-27  9:22                                       ` Richard Purdie
2009-03-24 19:59         ` Mike (mwester)

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=49CAC438.2020907@dls.net \
    --to=mwester@dls.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.