why does quick start guide refer to non-provided "poky-image-sato"?


Robert P. J. Day
 

maybe i'm misreading something, but the yocto QS guide provides the
sample command:

$ bitbake -k poky-image-sato

however, nothing provides that target. i can see the git log entry:

commit 1947b17478187bb623da74484747e470ce42d206
Author: Scott Rifenbark <scott.m.rifenbark@...>
Date: Tue May 10 12:50:36 2011 -0500

documentation/yocto-project-qs/yocto-project-qs.xml: changed build command

The command used in the example to build an image was using
'bitbake core-image-sato', which is only available in master and
not Bernard. So, I changed the command to be 'bitbake poky-image-sato'
at Dave Stewart's request. He located and pointed out the error.

(From yocto-docs rev: 3fa83550aaec5a3549825814a77fa7a823a2daea)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@...>
Signed-off-by: Richard Purdie <richard.purdie@...>

but it seems that "core-image-sato" is perfectly valid, at least at
the moment. clarification?

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================


Rifenbark, Scott M <scott.m.rifenbark@...>
 

Robert,

My understanding was that the target for this sample command could not be 'core-image-sato' for the QS version on the website, which supports Bernard. Maybe someone out there has a bit more information on details to your question.

ScottR

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Robert P. J. Day
Sent: Thursday, July 14, 2011 2:32 PM
To: Yocto discussion list
Subject: [yocto] why does quick start guide refer to non-provided "poky-image-sato"?


maybe i'm misreading something, but the yocto QS guide provides the
sample command:

$ bitbake -k poky-image-sato

however, nothing provides that target. i can see the git log entry:

commit 1947b17478187bb623da74484747e470ce42d206
Author: Scott Rifenbark <scott.m.rifenbark@...>
Date: Tue May 10 12:50:36 2011 -0500

documentation/yocto-project-qs/yocto-project-qs.xml: changed build command

The command used in the example to build an image was using
'bitbake core-image-sato', which is only available in master and
not Bernard. So, I changed the command to be 'bitbake poky-image-sato'
at Dave Stewart's request. He located and pointed out the error.

(From yocto-docs rev: 3fa83550aaec5a3549825814a77fa7a823a2daea)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@...>
Signed-off-by: Richard Purdie <richard.purdie@...>

but it seems that "core-image-sato" is perfectly valid, at least at
the moment. clarification?

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Robert P. J. Day
 

On Thu, 14 Jul 2011, Rifenbark, Scott M wrote:

Robert,

My understanding was that the target for this sample command could
not be 'core-image-sato' for the QS version on the website, which
supports Bernard. Maybe someone out there has a bit more
information on details to your question.

ScottR

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Robert P. J. Day
Sent: Thursday, July 14, 2011 2:32 PM
To: Yocto discussion list
Subject: [yocto] why does quick start guide refer to non-provided "poky-image-sato"?


maybe i'm misreading something, but the yocto QS guide provides the
sample command:

$ bitbake -k poky-image-sato

however, nothing provides that target. i can see the git log entry:

commit 1947b17478187bb623da74484747e470ce42d206
Author: Scott Rifenbark <scott.m.rifenbark@...>
Date: Tue May 10 12:50:36 2011 -0500

documentation/yocto-project-qs/yocto-project-qs.xml: changed build command

The command used in the example to build an image was using
'bitbake core-image-sato', which is only available in master and
not Bernard. So, I changed the command to be 'bitbake poky-image-sato'
at Dave Stewart's request. He located and pointed out the error.

(From yocto-docs rev: 3fa83550aaec5a3549825814a77fa7a823a2daea)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@...>
Signed-off-by: Richard Purdie <richard.purdie@...>

but it seems that "core-image-sato" is perfectly valid, at least at
the moment. clarification?
currently, scripts/oe-setup-builddir lists one of the common targets
as "core-image-sato", so certainly *something* is out of sync.

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================


Rifenbark, Scott M <scott.m.rifenbark@...>
 

Robert,

What release of Yocto Project are you using?

Scott

-----Original Message-----
From: Robert P. J. Day [mailto:rpjday@...]
Sent: Thursday, July 14, 2011 3:01 PM
To: Rifenbark, Scott M
Cc: Yocto discussion list
Subject: RE: [yocto] why does quick start guide refer to non-provided "poky-image-sato"?

On Thu, 14 Jul 2011, Rifenbark, Scott M wrote:

Robert,

My understanding was that the target for this sample command could
not be 'core-image-sato' for the QS version on the website, which
supports Bernard. Maybe someone out there has a bit more
information on details to your question.

ScottR

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Robert P. J. Day
Sent: Thursday, July 14, 2011 2:32 PM
To: Yocto discussion list
Subject: [yocto] why does quick start guide refer to non-provided "poky-image-sato"?


maybe i'm misreading something, but the yocto QS guide provides the
sample command:

$ bitbake -k poky-image-sato

however, nothing provides that target. i can see the git log entry:

commit 1947b17478187bb623da74484747e470ce42d206
Author: Scott Rifenbark <scott.m.rifenbark@...>
Date: Tue May 10 12:50:36 2011 -0500

documentation/yocto-project-qs/yocto-project-qs.xml: changed build command

The command used in the example to build an image was using
'bitbake core-image-sato', which is only available in master and
not Bernard. So, I changed the command to be 'bitbake poky-image-sato'
at Dave Stewart's request. He located and pointed out the error.

(From yocto-docs rev: 3fa83550aaec5a3549825814a77fa7a823a2daea)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@...>
Signed-off-by: Richard Purdie <richard.purdie@...>

but it seems that "core-image-sato" is perfectly valid, at least at
the moment. clarification?
currently, scripts/oe-setup-builddir lists one of the common targets
as "core-image-sato", so certainly *something* is out of sync.

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================


Joshua Lock <josh@...>
 

On Thu, 2011-07-14 at 18:01 -0400, Robert P. J. Day wrote:
On Thu, 14 Jul 2011, Rifenbark, Scott M wrote:

Robert,

My understanding was that the target for this sample command could
not be 'core-image-sato' for the QS version on the website, which
supports Bernard. Maybe someone out there has a bit more
information on details to your question.

ScottR

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Robert P. J. Day
Sent: Thursday, July 14, 2011 2:32 PM
To: Yocto discussion list
Subject: [yocto] why does quick start guide refer to non-provided "poky-image-sato"?


maybe i'm misreading something, but the yocto QS guide provides the
sample command:

$ bitbake -k poky-image-sato

however, nothing provides that target. i can see the git log entry:

commit 1947b17478187bb623da74484747e470ce42d206
Author: Scott Rifenbark <scott.m.rifenbark@...>
Date: Tue May 10 12:50:36 2011 -0500

documentation/yocto-project-qs/yocto-project-qs.xml: changed build command

The command used in the example to build an image was using
'bitbake core-image-sato', which is only available in master and
not Bernard. So, I changed the command to be 'bitbake poky-image-sato'
at Dave Stewart's request. He located and pointed out the error.

(From yocto-docs rev: 3fa83550aaec5a3549825814a77fa7a823a2daea)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@...>
Signed-off-by: Richard Purdie <richard.purdie@...>

but it seems that "core-image-sato" is perfectly valid, at least at
the moment. clarification?
currently, scripts/oe-setup-builddir lists one of the common targets
as "core-image-sato", so certainly *something* is out of sync.
As I understand it documentation repository updates are reflected on the
website so the docs tend to reflect the released version.

It would be nice to be able to provide development & release
documentation but I can't see it happening any time soon.

Joshua
--
Joshua Lock
Yocto Project "Johannes Factotum"
Intel Open Source Technology Centre


Robert P. J. Day
 

On Thu, 14 Jul 2011, Joshua Lock wrote:

As I understand it documentation repository updates are reflected on
the website so the docs tend to reflect the released version.

It would be nice to be able to provide development & release
documentation but I can't see it happening any time soon.
ok, that explains it but it doesn't defend it. IMHO, any single
versioned tarball or repository checkout should always be internally
consistent, and that includes embedded documentation. when i do a
"git pull" of any software, i expect the contents of any docs/
directory to reflect what's there.

if you want to publicly publish the docs that reflect the last
official release, then build those docs from the appropriate git tag.

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================


Richard Purdie
 

On Thu, 2011-07-14 at 19:10 -0400, Robert P. J. Day wrote:
On Thu, 14 Jul 2011, Joshua Lock wrote:

As I understand it documentation repository updates are reflected on
the website so the docs tend to reflect the released version.

It would be nice to be able to provide development & release
documentation but I can't see it happening any time soon.
ok, that explains it but it doesn't defend it. IMHO, any single
versioned tarball or repository checkout should always be internally
consistent, and that includes embedded documentation. when i do a
"git pull" of any software, i expect the contents of any docs/
directory to reflect what's there.

if you want to publicly publish the docs that reflect the last
official release, then build those docs from the appropriate git tag.
I agree that the docs in master should reflect the code in master and
that the docs on the bernard branch should be the ones which make the
bernard references.

Which or both can end up on the website as needed which is a separate
issue.

I thought this had been fixed and Scott had two branches so what's going
wrong? :/

Cheers,

Richard


Rifenbark, Scott M <scott.m.rifenbark@...>
 

I do have two branches (master and Bernard) in my yocto-docs contrib area. The master branch is used for updates to the upcoming release and is in various states of correctness/completeness. I guess I will need to take the time to do a push for every change I make to my local copy of yocto-docs master.

The docs that are on the website are Bernard only until we release.

ScottR

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Richard Purdie
Sent: Thursday, July 14, 2011 4:15 PM
To: Robert P. J. Day
Cc: yocto@...
Subject: Re: [yocto] why does quick start guide refer to non-provided "poky-image-sato"?

On Thu, 2011-07-14 at 19:10 -0400, Robert P. J. Day wrote:
On Thu, 14 Jul 2011, Joshua Lock wrote:

As I understand it documentation repository updates are reflected on
the website so the docs tend to reflect the released version.

It would be nice to be able to provide development & release
documentation but I can't see it happening any time soon.
ok, that explains it but it doesn't defend it. IMHO, any single
versioned tarball or repository checkout should always be internally
consistent, and that includes embedded documentation. when i do a
"git pull" of any software, i expect the contents of any docs/
directory to reflect what's there.

if you want to publicly publish the docs that reflect the last
official release, then build those docs from the appropriate git tag.
I agree that the docs in master should reflect the code in master and
that the docs on the bernard branch should be the ones which make the
bernard references.

Which or both can end up on the website as needed which is a separate
issue.

I thought this had been fixed and Scott had two branches so what's going
wrong? :/

Cheers,

Richard

_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto