From: Rod Whitby <rod@whitby.id.au>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Getting Started -Makefile
Date: Wed, 21 Nov 2007 07:49:52 +1030 [thread overview]
Message-ID: <47434F78.3040205@whitby.id.au> (raw)
In-Reply-To: <4742D2C0.7090805@student.utwente.nl>
Koen Kooi wrote:
> Rod Whitby schreef:
>> Isn't the creator of the OpenMoko build environment an OE core team
>> member? Does the OpenMoko build environment setup documentation follow
>> your prescription for TMPDIR and multimachine?
>
> Mickey was and is an OE core developer, but all the other core members
> have been appalled by the implementation of the OM env described in
> their wiki (to mention a few: hardcoding BUILD_ARCH and replacing
> /usr/bin/svn with a script).
So are you saying that the very first OM wiki how-to-build documentation
(which predated any MokoMakefile) was written by someone other than
Mickey, and that Mickey did not agree with the public release of the
description of how to build OpenMoko using OE? I find that incredulous.
> As proven multiple times on the OE-devel list, the OM wiki has bad
> practices for using OE. At the last OEDEM we coined 'Mo(c)kumentation'
> to describe it.
Yes, and you continue to disparage the OpenMoki wiki documentation,
instead of helping to fix it.
-- Rod
next prev parent reply other threads:[~2007-11-20 21:22 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 12:08 Getting Started -Makefile David Farning
2007-11-19 14:33 ` Koen Kooi
2007-11-19 23:51 ` Rod Whitby
2007-11-20 9:12 ` pHilipp Zabel
2007-11-20 17:57 ` Tim Bird
2007-11-20 20:00 ` Cliff Brake
2007-11-20 20:38 ` Philip Balister
2007-11-20 23:25 ` Florian Boor
2007-11-21 2:24 ` Paul Sokolovsky
2007-11-21 3:38 ` Rod Whitby
2007-11-21 2:24 ` Paul Sokolovsky
2007-11-21 5:44 ` Rod Whitby
2007-11-21 17:45 ` Paul Sokolovsky
2007-11-22 1:35 ` Michael 'Mickey' Lauer
2007-11-22 4:20 ` Lorn Potter
2007-11-22 8:14 ` Esben Haabendal
2007-11-23 1:05 ` Lorn Potter
2007-11-21 17:58 ` Tim Bird
2007-11-21 18:29 ` Paul Sokolovsky
2007-11-21 23:17 ` Rod Whitby
2007-11-22 0:44 ` Tim Bird
2007-11-22 20:29 ` Paul Sokolovsky
2007-11-21 19:32 ` Philip Balister
2007-11-21 19:32 ` Philip Balister
2007-11-20 21:16 ` Rod Whitby
2007-11-21 6:20 ` Esben Haabendal
2007-11-21 17:57 ` Paul Sokolovsky
2007-11-21 23:04 ` Rod Whitby
2007-11-22 8:40 ` Esben Haabendal
2007-11-20 9:39 ` Richard Purdie
2007-11-20 11:06 ` Rod Whitby
2007-11-20 12:30 ` Koen Kooi
2007-11-20 21:20 ` Rod Whitby
2007-11-20 9:58 ` Koen Kooi
2007-11-20 11:11 ` Rod Whitby
2007-11-20 12:27 ` Koen Kooi
2007-11-20 21:19 ` Rod Whitby [this message]
2007-11-20 14:39 ` Paul Sokolovsky
2007-11-20 23:20 ` Florian Boor
2007-11-20 11:44 ` Rod Whitby
2007-11-20 13:10 ` Koen Kooi
2007-11-20 21:11 ` Rod Whitby
2007-11-20 23:06 ` Lorn Potter
2007-11-19 14:41 ` Holger Freyther
2007-11-19 18:32 ` Tobias Pflug
2007-11-19 21:08 ` Lorn Potter
2007-11-20 9:33 ` Richard Purdie
2007-11-20 10:46 ` Marcin Juszkiewicz
2007-11-20 15:32 ` Mike (mwester)
2007-11-20 17:04 ` Marcin Juszkiewicz
2007-11-20 17:29 ` Holger Freyther
2007-11-20 17:29 ` Koen Kooi
2007-11-20 23:12 ` Lorn Potter
2007-11-22 1:32 ` Michael 'Mickey' Lauer
2007-11-22 1:28 ` The truth about OE team being afraid of 'make' (was: Getting Started -Makefile) Michael 'Mickey' Lauer
2007-11-22 3:15 ` Chris Larson
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=47434F78.3040205@whitby.id.au \
--to=rod@whitby.id.au \
--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.