From: Sven Ebenfeld <sven.ebenfeld@gmail.com>
To: ss infod <ssinfod@gmail.com>,
"meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>
Subject: Re: Angstrom for i.mx 6
Date: Mon, 09 Mar 2015 18:35:24 +0100 [thread overview]
Message-ID: <54FDD9DC.8060301@gmail.com> (raw)
In-Reply-To: <CAHUo2cyX6Dkvt2DGC0sbV=u=QLzy-yWv7dJLh=ckk5uCic96Vg@mail.gmail.com>
Am 08.03.2015 um 06:26 schrieb ss infod:
> Thanks for your response. My image is building right now.
>
> I have one more question related to Angstrom and Yocto/Poky:
> Is there any reason to use Angstrom instead of Yocto/Poky ?
> Is Angstrom outdated ?
My experience is, that Angstrom is updated very quickly when new
releases of OpenEmbedded-layers are released. So I would not at all say
that Angstrom is outdated.
>
> I'm looking for a embeded distro that has package management connected to
> "public repository". (I mean that I can install package like "apt-get
> install xyz" from the target)
> I think Angstrom has public repository.. Is that right ?
I've never used the public repositories as we are building only devices
with read-only rootfs and without package manager. So I can't give an
answer to this.
But one reason for me to decide for Angstrom was the online build system
which made it quite easy to get started.
>
> The problem I have with yocto is that it seems there is no "public
> repository". It seems you need to include the package in the build.
> Is there any "public repostiory" that hosts packages for Yocto. (which can
> be installed from the target post build)
>
> Thanks
> ssinfod
>
prev parent reply other threads:[~2015-03-09 17:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 4:14 Angstrom for i.mx 6 ss infod
2015-03-05 7:38 ` Sven Ebenfeld
2015-03-05 17:56 ` ss infod
2015-03-05 18:05 ` Sven Ebenfeld
2015-03-05 18:05 ` Sven Ebenfeld
2015-03-08 5:26 ` ss infod
2015-03-09 17:35 ` Sven Ebenfeld [this message]
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=54FDD9DC.8060301@gmail.com \
--to=sven.ebenfeld@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=ssinfod@gmail.com \
/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.