From: Marko Lindqvist <cazfi74@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] gnomebase.bbclass improvements
Date: Fri, 7 Jun 2013 00:55:40 +0300 [thread overview]
Message-ID: <cover.1370555136.git.cazfi74@gmail.com> (raw)
A couple of gnomebase.bbclass changes from the tree where I've been
working to include recipe for latest (gtk3-only) vte version in addition
to older gtk2-compatible one.
trim_version() -patch should't be any way controversial.
GNOMEBN -patch is one you may want to apply now, or to wait if there
is going to be any users for the feature and apply only when
actually needed.
The following changes since commit 8a2ac668d99f7d64c2acffc3a39cedb2d152be6e:
lrzsz: check locale.h in configure (2013-06-04 15:53:45 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib cazfi/misc
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=cazfi/misc
Marko Lindqvist (2):
gnomebase.bbclass: implement gnome_verdir() using trim_version()
gnomebase.bbclass: add support for archive name different from BPN
meta/classes/gnomebase.bbclass | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
--
1.7.10.4
reply other threads:[~2013-06-06 21:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cover.1370555136.git.cazfi74@gmail.com \
--to=cazfi74@gmail.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