* uclibc recipes in oe-core versioning & using upstream
@ 2014-11-14 16:21 Brendan Le Foll
2014-11-15 3:02 ` Khem Raj
0 siblings, 1 reply; 2+ messages in thread
From: Brendan Le Foll @ 2014-11-14 16:21 UTC (permalink / raw)
To: openembedded-core
I'm trying to understand the logic behind the uclibc recipes, it seems
it is using fairly random points in history of git master and not the
0.9.33 point releases that have been made.
What is the logic behind that and why not use the upstream release
builds as a starting point?
Thanks,
Brendan
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: uclibc recipes in oe-core versioning & using upstream
2014-11-14 16:21 uclibc recipes in oe-core versioning & using upstream Brendan Le Foll
@ 2014-11-15 3:02 ` Khem Raj
0 siblings, 0 replies; 2+ messages in thread
From: Khem Raj @ 2014-11-15 3:02 UTC (permalink / raw)
To: Brendan Le Foll; +Cc: Patches and discussions about the oe-core layer
On Fri, Nov 14, 2014 at 8:21 AM, Brendan Le Foll
<brendan.le.foll@intel.com> wrote:
> I'm trying to understand the logic behind the uclibc recipes, it seems
> it is using fairly random points in history of git master and not the
> 0.9.33 point releases that have been made.
>
> What is the logic behind that and why not use the upstream release
> builds as a starting point?
last uclibc release has been long time ago. We need newer features
especially for systemd to work.
are you seeing some issues with what we have ? and its always top of
master. We pick a master version
and then stabilize it to whatever we can. btw. uclibc master does not
move at a faster pace where it breaks often
so its ok to use it.
>
> Thanks,
> Brendan
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-11-15 3:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-11-14 16:21 uclibc recipes in oe-core versioning & using upstream Brendan Le Foll
2014-11-15 3:02 ` Khem Raj
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).