From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Patch for libfann-2.0.0 recipe
Date: Thu, 18 Jun 2009 19:52:21 +0200 [thread overview]
Message-ID: <h1dusl$4lp$1@ger.gmane.org> (raw)
In-Reply-To: <be7a9f3d0906180952v1bbb0611kd7079d5d947f83b8@mail.gmail.com>
On 18-06-09 18:52, Otavio Salvador wrote:
> Hello Koen,
>
> On Thu, Jun 18, 2009 at 1:48 PM, Koen Kooi<k.kooi@student.utwente.nl> wrote:
>>> PR = "r01"
>>
>> Don't set PR to that.
>
> I believe that most people prefer to always have PR field included;
> obviously it ought to be PR = "r1" or PR = "r0" but it is harder to
> forget to update it when it shows in the recipe.
That's nonsense. Not setting PR = "r0" in recipes makes maintenance a
lot easier, e.g. forcing rebuild or all xorg libs. If every recipe was
already using INC_PR, I might agree with you, but since that isn't the
case adding PR = "r0" is creating more work.
regards,
Koen
next prev parent reply other threads:[~2009-06-18 18:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 17:14 Patch for libfann-2.0.0 recipe Elvis Dowson
2009-06-16 18:27 ` Koen Kooi
2009-06-16 18:38 ` Philip Balister
2009-06-16 19:00 ` Elvis Dowson
2009-06-16 19:59 ` Philip Balister
2009-06-16 21:36 ` Koen Kooi
2009-06-17 4:43 ` Rolf Leggewie
2009-06-18 16:05 ` Elvis Dowson
2009-06-18 16:48 ` Koen Kooi
2009-06-18 16:52 ` Otavio Salvador
2009-06-18 17:52 ` Koen Kooi [this message]
2009-06-18 18:11 ` Philip Balister
2009-06-18 18:24 ` Koen Kooi
2009-06-18 23:05 ` Tom Rini
2009-06-19 1:28 ` Otavio Salvador
2009-06-19 8:06 ` Koen Kooi
2009-06-19 17:47 ` Tom Rini
2009-06-19 17:53 ` Koen Kooi
2009-06-18 18:09 ` Philip Balister
2009-06-18 18:14 ` Koen Kooi
2009-06-18 18:36 ` Elvis Dowson
2009-06-18 18:56 ` Philip Balister
2009-06-19 13:37 ` Philip Balister
2009-06-19 13:52 ` Elvis Dowson
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='h1dusl$4lp$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox