Openembedded Core Discussions
 help / color / mirror / Atom feed
* Heads Up: Bitbake minimum version change imminent
@ 2011-06-28 14:31 Richard Purdie
  2011-06-28 16:26 ` Chris Larson
  0 siblings, 1 reply; 3+ messages in thread
From: Richard Purdie @ 2011-06-28 14:31 UTC (permalink / raw)
  To: openembedded-core

I just wanted to let people know that we have a minimum version of
bitbake change imminent for OE-Core.

I've already pushed the changes we need to bitbake for umask, shared
work directory and multilib and updated its version to 1.13.2. I'm
planning to merge patches to OE-Core which depend on these changes later
this week (and bump the minimum version OE-Core requires at the same
time).

In case it isn't clear, I've been batching things up to try and ensure
we only have to do this once for a variety of improvements :)

Cheers,

Richard




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Heads Up: Bitbake minimum version change imminent
  2011-06-28 14:31 Heads Up: Bitbake minimum version change imminent Richard Purdie
@ 2011-06-28 16:26 ` Chris Larson
  2011-07-05 14:42   ` Richard Purdie
  0 siblings, 1 reply; 3+ messages in thread
From: Chris Larson @ 2011-06-28 16:26 UTC (permalink / raw)
  To: Patches and discussions about the oe-core layer

On Tue, Jun 28, 2011 at 7:31 AM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> I just wanted to let people know that we have a minimum version of
> bitbake change imminent for OE-Core.
>
> I've already pushed the changes we need to bitbake for umask, shared
> work directory and multilib and updated its version to 1.13.2. I'm
> planning to merge patches to OE-Core which depend on these changes later
> this week (and bump the minimum version OE-Core requires at the same
> time).
>
> In case it isn't clear, I've been batching things up to try and ensure
> we only have to do this once for a variety of improvements :)

I have to say that it's *extremely* unintuitive to have a minimum
version requirement on a version that hasn't even been tagged in the
git repository. If it's good enough to depend on, it should be good
enough to consider released.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Heads Up: Bitbake minimum version change imminent
  2011-06-28 16:26 ` Chris Larson
@ 2011-07-05 14:42   ` Richard Purdie
  0 siblings, 0 replies; 3+ messages in thread
From: Richard Purdie @ 2011-07-05 14:42 UTC (permalink / raw)
  To: Patches and discussions about the oe-core layer

On Tue, 2011-06-28 at 09:26 -0700, Chris Larson wrote:
> On Tue, Jun 28, 2011 at 7:31 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > I just wanted to let people know that we have a minimum version of
> > bitbake change imminent for OE-Core.
> >
> > I've already pushed the changes we need to bitbake for umask, shared
> > work directory and multilib and updated its version to 1.13.2. I'm
> > planning to merge patches to OE-Core which depend on these changes later
> > this week (and bump the minimum version OE-Core requires at the same
> > time).
> >
> > In case it isn't clear, I've been batching things up to try and ensure
> > we only have to do this once for a variety of improvements :)
> 
> I have to say that it's *extremely* unintuitive to have a minimum
> version requirement on a version that hasn't even been tagged in the
> git repository. If it's good enough to depend on, it should be good
> enough to consider released.

Agreed and I did add the tags.

Cheers,

Richard




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2011-07-05 14:46 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-06-28 14:31 Heads Up: Bitbake minimum version change imminent Richard Purdie
2011-06-28 16:26 ` Chris Larson
2011-07-05 14:42   ` Richard Purdie

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox