All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] wpa-gui-e: build the latest version from git sources
Date: Wed, 25 May 2011 16:12:45 +0200	[thread overview]
Message-ID: <irj2ot$fj8$1@dough.gmane.org> (raw)
In-Reply-To: <1306332204.10056.81.camel@mattotaupa>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 25-05-11 16:03, Paul Menzel wrote:
> Dear Andreas, dear Eyal,
> 
> 
> On Mi, 2011-05-25 at 15:36 +0200, Andreas Oberritter wrote:
> 
>> On 05/25/2011 02:58 PM, Eyal Reizer wrote:
> 
> […]
> 
>>> +SRCREV = "b8fb017272ed4794339978c9fbc0e74571a44728"
>>> +PR = "r0"
>>
>> PR = "r0" is the default and can be removed.
> 
> it seems there are different opinions on this topic. At least the manual
> says differently.
> 
>         Note
>         
>         It is good practice to always define PR in your recipes, even
>         for the "r0" release, so that when editing the recipe it is
>         clear that the PR number needs to be updated.
>         
>         You should always increment PR when modifying a recipe.
>         Sometimes this can be avoided if the change will have no effect
>         on the actual packages generated by the recipe, such as updating
>         the SRC_URI to point to a new host. If in any doubt then you
>         should increase the PR regardless of what has been changed.
>         
>         The PR value should never be decremented. If you accidentally
>         submit a large PR value for example then it should be left at
>         the value and just increased for new releases, not reset back to
>         a lower version.
> 
>>> +PV = "0.7.3+0.8.0-rc"
>>> +PR_append = "+gitr${SRCPV}"
>>
>> SRCPV should not be used in PR (even if it's been copied from another
>> recipe which does it wrong).
> 
> I am still confused about this one. That is why I still have not
> committed the pkg-config patch yet [2]. Could the right way be
> documented in the manual.

It is completely OK to use it in PR if you want the hash in PR, but not PV.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFN3Q5dMkyGM64RGpERAhwhAKCKxo/HdbjYY90JHWbgtyiGCMwLFQCgiaRa
HB1AMRMFaS/r4+iF6S6wa5M=
=XI4d
-----END PGP SIGNATURE-----




  reply	other threads:[~2011-05-25 14:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 12:58 [PATCH] wpa-gui-e: build the latest version from git sources Eyal Reizer
2011-05-25 13:13 ` Henning Heinold
2011-05-25 13:19 ` Paul Menzel
2011-05-25 13:36 ` Andreas Oberritter
2011-05-25 14:03   ` Paul Menzel
2011-05-25 14:12     ` Koen Kooi [this message]
2011-05-25 14:18       ` Reizer, Eyal
2011-05-25 14:25         ` Martin Jansa

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='irj2ot$fj8$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.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.