Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: Request to move "gitpkgv.bbclass" from meta-oe to oe-core
Date: Wed, 8 Oct 2014 16:39:57 +0200	[thread overview]
Message-ID: <54354CBD.6040506@topic.nl> (raw)

The gitpkgv class is very helpful when you want packages to have a consistent 
incremental version number, when build machines cannot talk to eachother 
(ruling out using PRSERVER for example) other than through repositories.

However, this small gem is present in meta-oe and not in the core. I now have 
several layers that pull in all of meta-oe just for being able to number GIT 
versions incrementally.

Could gitpkgv be moved into oe-core? (I'll be happy to write and submit the 
patch.) Or, is there an alternative that does something similar?

Kind regards,
Mike.


Met vriendelijke groet / kind regards,

Mike Looijmans

TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Topic zoekt gedreven (embedded) software specialisten!
http://topic.nl/vacatures/topic-zoekt-software-engineers/



             reply	other threads:[~2014-10-08 14:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08 14:39 Mike Looijmans [this message]
2014-10-09  8:16 ` Request to move "gitpkgv.bbclass" from meta-oe to oe-core Mike Looijmans
2014-10-09 19:56   ` Richard Purdie
2014-10-09 22:15     ` Otavio Salvador
2014-10-10  5:36       ` Mike Looijmans
2014-10-10 15:03         ` Paul Eggleton
2014-10-20 14:00           ` Mike Looijmans
2014-11-03 14:18             ` Mike Looijmans

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=54354CBD.6040506@topic.nl \
    --to=mike.looijmans@topic.nl \
    --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