All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] vala-dbus-binding-tool: relocate native recipe from freesmartphone subdir
Date: Sat, 13 Feb 2010 14:26:56 +0100	[thread overview]
Message-ID: <20100213132656.GE5364@jama> (raw)
In-Reply-To: <4B756FA7.2080800@dresearch.de>

On Fri, Feb 12, 2010 at 04:11:35PM +0100, Steffen Sledz wrote:
> Martin Jansa wrote:
> >>  .../vala-dbus-binding-tool-native_git.bb           |   10 ----------
> >>  .../vala-dbus-binding-tool-native_git.bb           |   10 ++++++++++
> >>  2 files changed, 10 insertions(+), 10 deletions(-)
> >>  delete mode 100644 recipes/freesmartphone/vala-dbus-binding-tool-native_git.bb
> >>  create mode 100644 recipes/vala-dbus-binding-tool/vala-dbus-binding-tool-native_git.bb
> > 
> > Why not use that non-native package or at least that new .inc file or
> > ideally BBCLASSEXTENDS?
> 
> Hmmm? I'm not really familiar with BBCLASSEXTENDS.

grep recipes for examples, but in short
if you add BBCLASSEXTENDS="native" in
vala-dbus-binding-tool_git.bb
it will be like having vala-dbus-binding-tool-native_git.bb with 
include for non-native and inherit native (and will save few seconds for
parsing second file I guess)

> I believe sharing recipe stuff between non-native and native
> packages i could realize like in recipes/vala/. But i've
> no idea how to bring the numbered version we need (0.1.3)
> together with the git version the freesmartphone guys use.

If you insist on having versioned recipe (good), then please add both
0.1.3 and git recipe with BBCLASSEXTENDS.

You can share all metadata except SRC_URI and S, between versioned and git.
Or even better, put generic SRC_URI (with ${PV} and name=archive) and then 
overwrite that only in git recipe. This way new version is created by just 
cp pn_pv.bb pn_pvNew.bb and update checksums in pn_pvNew.bb.

> Anyone an example for this?

yes in recipes/* :)

-- 
uin:136542059                jid:Martin.Jansa@gmail.com
Jansa Martin                 sip:jamasip@voip.wengo.fr 
JaMa                         



  reply	other threads:[~2010-02-13 13:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09 13:33 vala-dbus-binding-tool? Steffen Sledz
2010-02-10  6:48 ` [PATCH] vala-dbus-binding-tool-0.1.3: new recipe Steffen Sledz
2010-02-10  7:12   ` Steffen Sledz
2010-02-10 13:21   ` Steffen Sledz
2010-02-11 13:18     ` Steffen Sledz
2010-02-11 13:21       ` Martin Jansa
2010-02-11 13:30         ` Steffen Sledz
2010-02-11 13:58       ` Paul Menzel
2010-02-11 15:52         ` Steffen Sledz
2010-02-11  8:40   ` Steffen Sledz
2010-02-11  8:47     ` Martin Jansa
2010-02-11 11:43       ` Steffen Sledz
2010-02-11 12:19         ` Dr. Michael Lauer
2010-02-11 15:51           ` [PATCH 1/2] " Steffen Sledz
2010-02-11 15:51             ` [PATCH 2/2] vala-dbus-binding-tool: relocate native recipe from freesmartphone subdir Steffen Sledz
2010-02-11 16:07               ` Martin Jansa
2010-02-12 15:11                 ` Steffen Sledz
2010-02-13 13:26                   ` Martin Jansa [this message]
2010-02-15 10:54                     ` [PATCH] vala-dbus-binding-tool: (mostly) new recipe Steffen Sledz
2010-02-15 12:26                       ` Michael 'Mickey' Lauer
2010-02-15 13:31                       ` Martin Jansa
2010-02-15 15:05                         ` Steffen Sledz
2010-02-16  6:55                           ` Steffen Sledz

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=20100213132656.GE5364@jama \
    --to=martin.jansa@gmail.com \
    --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.