From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Iorga, Cristian" <cristian.iorga@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Package recipes change proposal (system-wide) - name wise
Date: Wed, 25 Jul 2012 11:09:57 +0100 [thread overview]
Message-ID: <17225760.ocbdZxpBHY@helios> (raw)
In-Reply-To: <969F26A8BAB325438E7EB80D3C3134FB16174E03@IRSMSX102.ger.corp.intel.com>
On Wednesday 25 July 2012 07:23:31 Iorga, Cristian wrote:
> For me, having the version number contained in the name of package recipe is
> a little bit puzzling. For example: libpcre/libpcre_8.31.bb
>
> Is there a solid technical reason to not have it like this?
>
> libpcre/libpcre.bb
> and inside the recipe to have a PV variable defined:
> PV="8.31"
The benefit of having PV in the recipe file name is that you can then easily
have different recipes for different versions of the same piece of software,
which is particularly useful when those different versions may need to be built
slightly differently.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-07-25 10:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 7:02 [PATCH 0/1] mtools: add glibc-gconv-* to RDEPENDS/RRECOMMENDS xin.ouyang
2012-07-25 7:02 ` [PATCH 1/1] " xin.ouyang
2012-07-26 19:04 ` Phil Blundell
2012-07-25 7:23 ` Package recipes change proposal (system-wide) - name wise Iorga, Cristian
2012-07-25 10:05 ` Koen Kooi
2012-07-25 10:09 ` Paul Eggleton [this message]
2012-07-25 13:48 ` Chris Larson
2012-07-26 19:52 ` Bruce Ashfield
2012-07-26 19:40 ` Richard Purdie
2012-07-26 20:44 ` Joshua Lock
2012-07-28 9:22 ` Anders Darander
2012-08-03 23:46 ` Darren Hart
2012-07-26 19:01 ` [PATCH 0/1] mtools: add glibc-gconv-* to RDEPENDS/RRECOMMENDS Saul Wold
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=17225760.ocbdZxpBHY@helios \
--to=paul.eggleton@linux.intel.com \
--cc=cristian.iorga@intel.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox