From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: <rant>the current yocto FAQ is pretty much valueless</rant>
Date: Wed, 27 Jun 2012 21:14:51 +0100 [thread overview]
Message-ID: <4FEB69BB.2080906@r-finger.com> (raw)
In-Reply-To: <83905E03-FF88-48EC-9336-273B02FB9FB1@beagleboard.org>
Hi Koen,
On 27/06/12 15:59, Koen Kooi wrote:
> Yocto is NOT a distro.
Is that so? :-), meta-yocto distro.conf:
DISTRO = "poky"
DISTRO_NAME = "Yocto (Built by Poky 7.0)"
DISTRO_VERSION = "1.2"
I am well aware that textual meaning is pretty much constructed by the
reader, and that authorial intent is an elusive concept, but I am ready
to argue that the conventional understanding of the above is that Poky
is a build tool, and Yocto is the public name of the distro that you
build if you use meta-yocto. To read that as 'Yocto is NOT a distro' I
think requires a definite pre-understanding that Yocto is not a distro,
which would need to come from some other source (or perhaps it is an
axiom of faith; myself, I tend hold firmly to the authority of the
source code alone). I shall not deny you the right to hold to such a
reading, but I do reserve the right to deconstruct it. :-)
> This thread highlights the reason the oe folks have been pushing to get rid of the 'poky' name completely
Perhaps one of the reasons; but then the erasure of Poky would mean that
you could no longer say 'Yocto is a NOT a distro', which I suspect would
achieve the very opposite of what you seek (and, perhaps more
importantly, might cost Dave and Saul a lunch or two). Personally, I
think much better solution would be if the distro was simply called Poky
v7.0, then we could all say 'Yocto is NOT a distro!' with conviction.
Plus Poky is such a lovely name, don't you think? ;-)
Tomas
next prev parent reply other threads:[~2012-06-27 20:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 9:09 <rant>the current yocto FAQ is pretty much valueless</rant> Robert P. J. Day
2012-06-26 9:35 ` Jack Mitchell
2012-06-26 9:55 ` Tomas Frydrych
2012-06-26 10:09 ` Paul Eggleton
2012-06-26 10:18 ` Robert P. J. Day
2012-06-26 15:46 ` Darren Hart
2012-06-26 16:06 ` Paul Eggleton
2012-06-26 16:38 ` Tomas Frydrych
2012-06-26 16:53 ` Robert P. J. Day
2012-06-26 17:18 ` Tomas Frydrych
2012-06-26 17:59 ` Brian Duffy
2012-06-27 9:39 ` Tomas Frydrych
2012-06-26 18:52 ` Tim Bird
2012-06-27 9:09 ` Tomas Frydrych
2012-06-27 14:59 ` Koen Kooi
2012-06-27 16:43 ` Chris Hallinan
2012-06-27 17:27 ` Koen Kooi
2012-06-27 20:14 ` Tomas Frydrych [this message]
2012-06-27 21:58 ` Koen Kooi
2012-06-28 7:44 ` Tomas Frydrych
2012-07-01 16:23 ` Philip Balister
2012-06-27 21:14 ` Philip Balister
2012-06-27 21:51 ` Philip Balister
2012-06-26 11:29 ` Koen Kooi
2012-06-26 14:40 ` Rifenbark, Scott M
2012-06-26 15:45 ` Robert P. J. Day
2012-06-26 15:50 ` Rifenbark, Scott M
2012-06-26 16:18 ` Paul Eggleton
2012-06-26 16:26 ` Robert P. J. Day
2012-06-26 16:33 ` Paul Eggleton
2012-06-26 16:51 ` Robert P. J. Day
2012-06-26 17:02 ` Paul Eggleton
2012-06-26 17:05 ` Robert P. J. Day
2012-06-26 17:09 ` Paul Eggleton
2012-06-26 17:14 ` Robert P. J. Day
2012-06-26 17:08 ` Rifenbark, Scott M
2012-06-26 17:12 ` Robert P. J. Day
2012-06-27 16:42 ` Jeff Osier-Mixon
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=4FEB69BB.2080906@r-finger.com \
--to=tf+lists.yocto@r-finger.com \
--cc=yocto@yoctoproject.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.