On 06/28/2012 03:44 AM, Tomas Frydrych wrote:
Hi Koen,
On 27/06/12 22:58, Koen Kooi wrote:
I have no problem with poky-the-distro, I have a problem with
poky-the-buildsystem. I warned mallum about this confusion years ago,
but you know how stubborn he can be :)
The Yocto naming confusion is e
Hi Koen,
On 27/06/12 22:58, Koen Kooi wrote:
> I have no problem with poky-the-distro, I have a problem with
> poky-the-buildsystem. I warned mallum about this confusion years ago,
> but you know how stubborn he can be :)
The Yocto naming confusion is entirely of Yocto making, nothing at all
to d
Op 27 jun. 2012 om 22:14 heeft Tomas Frydrych het
volgende geschreven:
> 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 a
On 06/26/2012 12:53 PM, Robert P. J. Day wrote:
On Tue, 26 Jun 2012, Tomas Frydrych wrote:
Kooen's cheeky point is worth keeping in mind though; the Yocto
naming semantics is not very helpful ;-) Specifically most of the
questions being asked on the Yocto list are about Poky, not Yocto,
followe
On 06/26/2012 12:53 PM, Robert P. J. Day wrote:
On Tue, 26 Jun 2012, Tomas Frydrych wrote:
Kooen's cheeky point is worth keeping in mind though; the Yocto
naming semantics is not very helpful ;-) Specifically most of the
questions being asked on the Yocto list are about Poky, not Yocto,
followe
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 inte
Op 27 jun. 2012 om 18:43 heeft Chris Hallinan het
volgende geschreven:
> On Wed, Jun 27, 2012 at 10:59 AM, Koen Kooi wrote:
>
>
> Op 27 jun. 2012 om 11:09 heeft Tomas Frydrych
> het volgende geschreven:
>
> > Hi Tim,
> >
> > On 26/06/12 19:52, Tim Bird wrote:
> >> On 06/26/2012 10:18 AM,
On Wed, Jun 27, 2012 at 10:59 AM, Koen Kooi wrote:
>
>
> Op 27 jun. 2012 om 11:09 heeft Tomas Frydrych
> het volgende geschreven:
>
> > Hi Tim,
> >
> > On 26/06/12 19:52, Tim Bird wrote:
> >> On 06/26/2012 10:18 AM, Tomas Frydrych wrote:
> >> For example, after reading various FAQs
> >> I still
Hi all - looks like it has been a busy morning while I wasn't looking!
I was the last one to touch the FAQ on the wiki, and I can attest that
its goal is not to be an end-all be-all technical FAQ, of the how-do-I
variety or any other. It should have more correct language in it, to
which I will att
Op 27 jun. 2012 om 11:09 heeft Tomas Frydrych het
volgende geschreven:
> Hi Tim,
>
> On 26/06/12 19:52, Tim Bird wrote:
>> On 06/26/2012 10:18 AM, Tomas Frydrych wrote:
>> For example, after reading various FAQs
>> I still have no idea what kind of thing "Poky" is. I know
>> that bitbake is
Hi,
On 26/06/12 18:59, Brian Duffy wrote:
> No, an FAQ should not get you the expertise to create a commercial grade
> product. Reading the documentation should though. You don't want users to
> have to study source code.
If you were paying for the tools, then that would be a reasonable
expectati
Hi Tim,
On 26/06/12 19:52, Tim Bird wrote:
> On 06/26/2012 10:18 AM, Tomas Frydrych wrote:
> For example, after reading various FAQs
> I still have no idea what kind of thing "Poky" is. I know
> that bitbake is a build tool. I know that OE is a package
> meta-information project. Yocto Project
On 06/26/2012 10:18 AM, Tomas Frydrych wrote:
> On 26/06/12 17:53, Robert P. J. Day wrote:
>> and if you want major industry players to take yocto seriously, the
>> last thing you want to do is answer their heartfelt pleas for
>> assistance with, "i'm sorry, that's technically not a yocto questio
No, an FAQ should not get you the expertise to create a commercial grade
product. Reading the documentation should though. You don't want users to
have to study source code.
On Tue, Jun 26, 2012 at 1:18 PM, Tomas Frydrych wrote:
> On 26/06/12 17:53, Robert P. J. Day wrote:
> > and if you want
On 26/06/12 17:53, Robert P. J. Day wrote:
> and if you want major industry players to take yocto seriously, the
> last thing you want to do is answer their heartfelt pleas for
> assistance with, "i'm sorry, that's technically not a yocto question,
> you should try another mailing list."
That's
On Tue, 26 Jun 2012, Paul Eggleton wrote:
> On Tuesday 26 June 2012 13:05:21 Robert P. J. Day wrote:
> > On Tue, 26 Jun 2012, Paul Eggleton wrote:
> > > On Tuesday 26 June 2012 12:51:15 Robert P. J. Day wrote:
> > > > ok, that makes sense. but would it also make sense for bitbake to
> > > > per
On Tue, 26 Jun 2012, Rifenbark, Scott M wrote:
> So this situation might lend itself to a nice FAQ question
> Something like "How do I isolate site and machine specific
> information during a build?" And the solution can tell them how to
> use a site.conf file.
yes, but it would also need
On Tuesday 26 June 2012 13:05:21 Robert P. J. Day wrote:
> On Tue, 26 Jun 2012, Paul Eggleton wrote:
> > On Tuesday 26 June 2012 12:51:15 Robert P. J. Day wrote:
> > > ok, that makes sense. but would it also make sense for bitbake to
> > > perhaps support another option that *does* allow persona
roject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Paul Eggleton
Sent: Tuesday, June 26, 2012 10:02 AM
To: Robert P. J. Day
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] the current yocto FAQ is pretty much valueless
On Tuesday 26 June 2012 12:51:15 Robert P. J. Day wrote:
> On Tue, 26 J
On Tue, 26 Jun 2012, Paul Eggleton wrote:
> On Tuesday 26 June 2012 12:51:15 Robert P. J. Day wrote:
> > On Tue, 26 Jun 2012, Paul Eggleton wrote:
> > > On Tuesday 26 June 2012 12:26:28 Robert P. J. Day wrote:
> > > > i thought that was the technique for centralizing personal config
> > > >
> >
On Tuesday 26 June 2012 12:51:15 Robert P. J. Day wrote:
> On Tue, 26 Jun 2012, Paul Eggleton wrote:
> > On Tuesday 26 June 2012 12:26:28 Robert P. J. Day wrote:
> > > i thought that was the technique for centralizing personal config
> > >
> > > preferences that you *didn't* want to manually cop
On Tue, 26 Jun 2012, Tomas Frydrych wrote:
> Kooen's cheeky point is worth keeping in mind though; the Yocto
> naming semantics is not very helpful ;-) Specifically most of the
> questions being asked on the Yocto list are about Poky, not Yocto,
> followed by questions about meta-yocto, not Yocto-
On Tue, 26 Jun 2012, Paul Eggleton wrote:
> On Tuesday 26 June 2012 12:26:28 Robert P. J. Day wrote:
> > i thought that was the technique for centralizing personal config
> > preferences that you *didn't* want to manually copy into every
> > local.conf file you created. if you add that personal
On 26/06/12 17:06, Paul Eggleton wrote:
> On Tuesday 26 June 2012 08:46:45 Darren Hart wrote:
>> On 06/26/2012 03:09 AM, Paul Eggleton wrote:
>>> I suggested to Scott R previously that it might be worth having a project
>>> FAQ (i.e., what is this project about, what is it intended to be used for
>
On Tuesday 26 June 2012 12:26:28 Robert P. J. Day wrote:
> i thought that was the technique for centralizing personal config
> preferences that you *didn't* want to manually copy into every
> local.conf file you created. if you add that personal content into
> each local.conf, then of course you
On Tue, 26 Jun 2012, Paul Eggleton wrote:
> On Tuesday 26 June 2012 11:45:50 Robert P. J. Day wrote:
> > since the ubiquitous reaction to complaining about something is
> > always, "don't just whine, do something about it," i'm doing that.
> > i've started a personal yocto FAQ, based on question
On Tuesday 26 June 2012 11:45:50 Robert P. J. Day wrote:
> since the ubiquitous reaction to complaining about something is
> always, "don't just whine, do something about it," i'm doing that.
> i've started a personal yocto FAQ, based on questions either i've
> asked myself, or colleagues or clie
On Tuesday 26 June 2012 08:46:45 Darren Hart wrote:
> On 06/26/2012 03:09 AM, Paul Eggleton wrote:
> > I suggested to Scott R previously that it might be worth having a project
> > FAQ (i.e., what is this project about, what is it intended to be used for
> > etc.) and a separate technical FAQ which
Great! Thanks Robert.
-Original Message-
From: Robert P. J. Day [mailto:rpj...@crashcourse.ca]
Sent: Tuesday, June 26, 2012 8:46 AM
To: Rifenbark, Scott M
Cc: Koen Kooi; Yocto discussion list
Subject: RE: [yocto] the current yocto FAQ is pretty much valueless
On Tue, 26 Jun 2012
On 06/26/2012 03:09 AM, Paul Eggleton wrote:
> On Tuesday 26 June 2012 05:09:34 Robert P. J. Day wrote:
>> in other words, a *good* FAQ might be:
>>
>> "how can i use the yocto prebuilt toolchains to save build time?"
>>
>> a *bad* FAQ would be:
>>
>> "Does the Yocto Project have a special go
On Tue, 26 Jun 2012, Rifenbark, Scott M wrote:
> Thanks all - I enjoyed the rant. The obvious point is that the FAQ
> needs attention. A good thing to do would be if you have a question
> that you would like included in a "good" FAQ, such as the one
> mentioned by Robert about how to add a singl
ginal Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Koen Kooi
Sent: Tuesday, June 26, 2012 4:30 AM
To: Robert P.J.Day
Cc: Yocto discussion list
Subject: Re: [yocto] the current yocto FAQ is pretty much valueless
Op 26 jun. 2012, om 11:09 heeft
Op 26 jun. 2012, om 11:09 heeft Robert P. J. Day het volgende geschreven:
>
> i mentioned this to scott rifenbark privately a few days ago, but i
> figured i might as well antagonize a few people on the list by saying
> it publicly -- the yocto FAQ as it stands is pretty much worthless.
>
> h
On Tue, 26 Jun 2012, Paul Eggleton wrote:
> On Tuesday 26 June 2012 05:09:34 Robert P. J. Day wrote:
> > in other words, a *good* FAQ might be:
> >
> > "how can i use the yocto prebuilt toolchains to save build time?"
> >
> > a *bad* FAQ would be:
> >
> > "Does the Yocto Project have a special
On Tuesday 26 June 2012 05:09:34 Robert P. J. Day wrote:
> in other words, a *good* FAQ might be:
>
> "how can i use the yocto prebuilt toolchains to save build time?"
>
> a *bad* FAQ would be:
>
> "Does the Yocto Project have a special governance model, or is it
> managed as an open source
On 26/06/12 10:09, Robert P. J. Day wrote:
> A bad Frequently Asked Questions (FAQ) sheet is one that is composed
> not of the questions people actually ask, but of the questions the
> FAQ's author wishes people would ask. Perhaps you've seen the type
> before:
Nice quote, but unfortunately based
On 26/06/12 10:09, Robert P. J. Day wrote:
snip...
in other words, a *good* FAQ might be:
"how can i use the yocto prebuilt toolchains to save build time?"
a *bad* FAQ would be:
"Does the Yocto Project have a special governance model, or is it
managed as an open source project?"
i mentioned this to scott rifenbark privately a few days ago, but i
figured i might as well antagonize a few people on the list by saying
it publicly -- the yocto FAQ as it stands is pretty much worthless.
https://wiki.yoctoproject.org/wiki/FAQ
by way of explanation, i'll reproduce the fir
38 matches
Mail list logo
