All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <joshua.lock@intel.com>
To: yocto@yoctoproject.org
Subject: Re: Documenting Poky dependencies
Date: Fri, 19 Nov 2010 12:38:41 +0000	[thread overview]
Message-ID: <1290170323.9343.8.camel@scimitar> (raw)
In-Reply-To: <B27EBC40D200ED48A3F4CC2EBEABAE0B25BC73A014@orsmsx501.amr.corp.intel.com>

On Thu, 2010-11-18 at 12:54 -0800, Stewart, David C wrote:
> Thanks for doing this! 
> 
> Some ScottR ARs below.
> 
> >From: yocto-bounces@yoctoproject.org [mailto:yocto-
> >bounces@yoctoproject.org] On Behalf Of Joshua Lock
> >Sent: Thursday, November 18, 2010 4:36 AM
> >
> >Hi all,
> >
> >I've been thinking about the issue of documenting Poky's dependencies in
> >the handbook.
> >At the moment the handbook includes a list of required packages and then
> >explicitly lists commands to install those packages on Ubuntu.
> >
> >What I'd like to propose is that we list the required dependencies in
> >the handbook and then link to a wiki page where we can list explicit
> >instructions for various distributions.
> >
> >This allows us to document the process for as many distributions as
> >possible without cluttering the handbook. An alternative would be to add
> >this to an appendix but I quite like the idea of people being able to
> >edit and add to this information without having to use git.
> >
> >To that end I've added a page to our public wiki showing the steps I had
> >to take to run Poky on Fedora and CentOS machines:
> >
> >https://wiki.yoctoproject.org/wiki/Poky/GettingStarted/Dependencies
> 
> Good idea. Some suggestions:
> 
> 1. There seem to be no links to this page from the rest of the wiki.
> Should add one. Scott - can you please figure out the best place?

Yeah, I wanted to make sure everyone was OK with the idea before I made
it too visible.

> 
> 2. Can you add something specific to the version of Poky (or Yocto)
> which has been verified with these distros? For example, f13 and f14
> have instructions for Laverne; they might change for a future rev. What
> is the best way to show this?

Not sure on the best way to show this, but this was Poky master (so
Laverne-ish) that I've tested.

I will verify that the steps work equally well for vanilla Laverne.

Cheers,
Joshua
-- 
Joshua Lock
        Intel Open Source Technology Centre

---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

  reply	other threads:[~2010-11-19 12:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 12:36 Documenting Poky dependencies Joshua Lock
2010-11-18 20:54 ` Stewart, David C
2010-11-19 12:38   ` Joshua Lock [this message]
2010-11-19 22:57     ` Darren Hart
2010-11-19 23:07       ` deVries, Alex

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=1290170323.9343.8.camel@scimitar \
    --to=joshua.lock@intel.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.