All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Boor <florian.boor@kernelconcepts.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] error out on .la files pointing to ${WORKDIR}
Date: Wed, 19 Mar 2008 12:24:53 +0100	[thread overview]
Message-ID: <47E0F805.4020706@kernelconcepts.de> (raw)
In-Reply-To: <3D9ECBB5-7C37-4D62-8D15-F2F0673EB867@student.utwente.nl>

Hi,

Koen Kooi schrieb:
> Things in stagin (e.g. .la files) point to ${WORKDIR} are broken and
> should die. If we want packaged-staging and rm_work to function we
> need to fix them. Since we are all lazy we need some incentive:

I'm not really a fan of enforcing things by breaking builds. I agree that we
need to fix this soon, but since some of this bugs are harmless and do not
affect the build at all I would not want to handle this that strict. If these
wrong files really break packaged-staging we get errors that force us to fix the
critical ones anyway.

Greetings

Florian

-- 
The dream of yesterday                  Florian Boor
is the hope of today                    Tel: +49 271-771091-15
and the reality of tomorrow.            Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904]        florian.boor@kernelconcepts.de

1D78 2D4D 6C53 1CA4 5588  D07B A8E7 940C 25B7 9A76



  reply	other threads:[~2008-03-19 11:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 10:50 [RFC] error out on .la files pointing to ${WORKDIR} Koen Kooi
2008-03-19 11:24 ` Florian Boor [this message]
2008-03-19 11:35   ` Koen Kooi
2008-03-19 12:23   ` Richard Purdie
2008-03-19 12:00 ` Stanislav Brabec
2008-03-19 12:35   ` Koen Kooi
2008-03-19 13:06     ` Stanislav Brabec
2008-03-19 12:22 ` Richard Purdie
2008-03-19 15:25   ` Koen Kooi
2008-03-19 22:26 ` 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=47E0F805.4020706@kernelconcepts.de \
    --to=florian.boor@kernelconcepts.de \
    --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.