Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: Otavio Salvador <otavio@ossystems.com.br>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Request to move "gitpkgv.bbclass" from meta-oe to oe-core
Date: Fri, 10 Oct 2014 07:36:25 +0200	[thread overview]
Message-ID: <54377059.10606@topic.nl> (raw)
In-Reply-To: <CAP9ODKpERB+agUBv3-BgPM3JRBQiZ-QKVhONvuSkRFUWi_ZkqQ@mail.gmail.com>

On 10/10/2014 12:15 AM, Otavio Salvador wrote:
> On Thu, Oct 9, 2014 at 4:56 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> On Thu, 2014-10-09 at 10:16 +0200, Mike Looijmans wrote:
>>> In partial reply to my own question, this has been discussed 2 years ago, but
>>> apparently nothing ever came out of it.
>>>
>>> http://lists.openembedded.org/pipermail/openembedded-core/2012-February/056050.html
>>>
>>> So once more the request to be able to get sane version strings for git repos.
>>> Can we please just move gitpkgv. That's like five minutes work, and if anyone
>>> (e.g. me) feels like building something better, he or she is free do submit
>>> that and get rid of the gitpkgv class once it's obsolete.
>>
>> I do feel quite strongly that this is something which should get
>> improved in the fetcher itself. That is why I've pushed back on the
>> patch since if I take it into OE-Core, there is even less incentive to
>> fix the real problem...
>
> Mike I am also an user of gitpkgv but I must to agree with Richard
> here. Moving this to OE-Core will just make it worse. It is way better
> to prepare a patch and add support for it on the fetcher code of
> BitBake.

Give me some pointers on what you're talking about here, and I'll be happy to 
try and implement it. Currently I have no idea as to what is "wrong" with the 
gitpkgv approach, and I also have no clue as to what it is you want to have 
implemented in the git fetcher.

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-10  5:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08 14:39 Request to move "gitpkgv.bbclass" from meta-oe to oe-core Mike Looijmans
2014-10-09  8:16 ` Mike Looijmans
2014-10-09 19:56   ` Richard Purdie
2014-10-09 22:15     ` Otavio Salvador
2014-10-10  5:36       ` Mike Looijmans [this message]
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=54377059.10606@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=richard.purdie@linuxfoundation.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