From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
rpjday@crashcourse.ca, openembedded-core@lists.openembedded.org
Subject: Re: worth adding a "git"-versioned of i2c-tools to oe-core?
Date: Mon, 31 Jul 2017 12:00:50 +0100 [thread overview]
Message-ID: <1501498850.18633.1.camel@linuxfoundation.org> (raw)
In-Reply-To: <ca8a860d-0894-e604-6108-359ccd094e72@linux.intel.com>
On Mon, 2017-07-31 at 13:41 +0300, Alexander Kanavin wrote:
> On 07/31/2017 01:41 PM, rpjday@crashcourse.ca wrote:
> >
> >
> > given that some significant changes have been made to i2c-tools
> > since
> > version 3.1.2, is it worth adding a git-versioned recipe of that
> > to
> > oe-core,
> > and using DEFAULT_PREFERENCE to force people to select it if they
> > want it?
> > in particular, the code base has been restructured, and a new
> > utility,
> > "i2ctransfer", has been added.
> It's better to ask the upstream to make a new release.
>
> We've had dual git/release recipes in the past, and they were all an
> utter failure. In the sense, that only one version of the recipe was
> maintained, and the other was completely neglected.
Going forward we may accept patches using this instead:
http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/classes/devupstream.bbclass
Cheers,
Richard
next prev parent reply other threads:[~2017-07-31 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 10:41 worth adding a "git"-versioned of i2c-tools to oe-core? rpjday
2017-07-31 10:41 ` Alexander Kanavin
2017-07-31 11:00 ` Richard Purdie [this message]
2017-07-31 11:15 ` rpjday
2017-07-31 12:50 ` Maxin B. John
2017-07-31 14:10 ` Maxin B. John
2017-07-31 19:17 ` Andre McCurdy
2017-07-31 18:57 ` Khem Raj
2017-08-01 13:35 ` Alexander Kanavin
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=1501498850.18633.1.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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.