All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: James Abernathy <jfabernathy@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: use case howto?
Date: Mon, 07 Nov 2011 15:04:52 -0700	[thread overview]
Message-ID: <4EB85604.50109@mlbassoc.com> (raw)
In-Reply-To: <CANFv2Ene=ZfVOzs76fsW7XNRm7K_0DNDB=q90AHV5Zs3KxcjNw@mail.gmail.com>

On 2011-11-07 14:59, James Abernathy wrote:
> I approach embedded Linux from a path of taking a Distro like Ubuntu or Fedora and chopping it down to a working set of code that forms the final solution.  Obviously, not the same
> methology as Yocto.  With some success with the current methods, it's difficult to see the advantages of Yocto.  I'm reading what I can find to get smarting on Yocto, but like most
> new concepts, you try to compare what you used to do with how to do it with the new concept.
> For example, if I use a distro, I can install packages really simply with yum or apt-get; update them the same way. If I start with a Yocto meta-??? that's closest to my hardware
> solution, and get it working at a base level, how do I add things, like browsers, or other application?

Using very similar tools - zypper is just like yum, or if
you choose to use ipk packages, opkg

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2011-11-07 22:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07 21:59 use case howto? James Abernathy
2011-11-07 22:04 ` Gary Thomas [this message]
2011-11-07 22:15   ` James Abernathy
2011-11-08  0:12     ` Gary Thomas
2011-11-08  0:38       ` James Abernathy
2011-11-07 22:50 ` Osier-mixon, Jeffrey

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=4EB85604.50109@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=jfabernathy@gmail.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.