All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Bitbake build error on Fedora 12 x86 64-bit
Date: Sun, 24 Jan 2010 08:50:39 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1001240845250.12002@localhost> (raw)
In-Reply-To: <201001231357.53005.holger+oe@freyther.de>

On Sat, 23 Jan 2010, Holger Hans Peter Freyther wrote:

> On Saturday 23 January 2010 13:38:08 Elvis Dowson wrote:

> > Hi, I found the solution for this. I was using the older svn
> > repository, and bitbake is now being maintained using the git
> > repository, which has the latest updates.
> >
> > Switching to the git version of the bitbake repository helped
> > remove the error, and the build has now commenced! :-)
>
> And in general we encourage users to use the release tarballs of
> Bitbake. This is why you should not be able to find your git
> commands in the documentation on OpenEmbedded.org

  just catching up on this thread ... i'm confused, what does it mean
to say, "you should not be able to find your git commands in the
documentation on OpenEmbedded.org"?  does that mean that the
development version of bitbake has additional commands above and
beyond the latest tarball release that aren't documented?  or what?

  also, while i appreciate that you encourage people to use the stable
version of bitbake, i don't think you should be so discouraging
regarding people who want to use the git checkout.  as long as people
realize it's a development version, why would you want to talk people
out of using it and helping you identify possible bugs?

  as long as users know the risks, i'd personally *encourage* them to
use the dev version, and reports bugs they find.  the more testers,
the better, no?

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================



  parent reply	other threads:[~2010-01-24 13:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19  8:01 git pull robin
2010-01-19  8:09 ` robin
2010-01-19 18:37   ` Paul Wilson
2010-01-23  7:22     ` Khem Raj
2010-01-23 11:16     ` Bitbake build error on Fedora 12 x86 64-bit Elvis Dowson
2010-01-23 12:38       ` Elvis Dowson
2010-01-23 12:57         ` Holger Hans Peter Freyther
2010-01-23 13:24           ` Elvis Dowson
2010-01-23 14:51             ` Paul Menzel
2010-01-23 19:40               ` Elvis Dowson
2010-01-23 16:38             ` Holger Hans Peter Freyther
2010-01-24 13:50           ` Robert P. J. Day [this message]
2010-01-24 15:10             ` Holger Hans Peter Freyther
2010-01-24 15:34               ` Robert P. J. Day
2010-01-25  2:45                 ` Holger Hans Peter Freyther
2010-01-25 11:49                   ` Robert P. J. Day
2010-01-25 12:15                     ` Koen Kooi
2010-01-25 12:35                       ` Robert P. J. Day
2010-01-23 12:39       ` Graeme Gregory
2010-01-27 16:54         ` Elvis Dowson
2010-01-19 20:13   ` git pull Bjørn Forsman

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=alpine.LFD.2.00.1001240845250.12002@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-devel@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 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.