From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Cc: angstrom-distro-devel@linuxtogo.org
Subject: Re: [Angstrom-devel] RFC: Add ipkg to minimal image
Date: Sun, 02 Dec 2007 11:31:14 +0000 [thread overview]
Message-ID: <1196595074.6648.11.camel@localhost.localdomain> (raw)
In-Reply-To: <475269FD.60409@student.utwente.nl>
On Sun, 2007-12-02 at 09:17 +0100, Koen Kooi wrote:
> Rod Whitby schreef:
> > Rod Whitby wrote:
> >> I just realised that minimal-image.bb doesn't include ipkg, whereas the
> >> first image which does include ipkg (console-image) includes a whole lot
> >> of other stuff which could be installed using ipkg after first boot and
> >> network access, and which make the image too big for a machine with
> >> limited flash space (like an NSLU2).
> >
> > RFC #1:
> >> Is there a reason why minimal-image does not include ipkg? What exactly
> >> is the definition of what should be in minimal-image which excludes the
> >> ability to install further packages?
>
> Marcin and I had a discussion about that, but I can't remember the
> outcome. So "I have no strong opinions on that".
I think minimal was really intended for people trying to boot systems
for the first time and really is 'the bare essentials to boot'. Having
said that I appreciate the problem of creating an image cut down enough
for the NSLU2.
Ideally, MACHINE=nslu2 should make the console image become small enough
to be usable for the device even if that different compared to the
minimal image is just the package manager due to size constraints...
On a related but different note, the presence of a package manager or
not sounds like an DISTRO_FEATURE. Perhaps we should add
"package-manager" as a DISTRO_FEATURE and then use this to decide
whether a package manager should be installed into an image. The package
manager to install should determined by the class building the image so
you end up with a package manager appropriate to the image - ipkg or
dpkg+apt currently.
Does that seem reasonable?
Cheers,
Richard
next prev parent reply other threads:[~2007-12-02 11:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 1:18 RFC: Add ipkg to minimal image Rod Whitby
2007-12-02 3:57 ` Rod Whitby
2007-12-02 8:17 ` [Angstrom-devel] " Koen Kooi
2007-12-02 10:08 ` Rod Whitby
2007-12-02 11:31 ` Richard Purdie [this message]
2007-12-02 12:54 ` Holger Freyther
2007-12-02 13:17 ` Koen Kooi
2007-12-02 15:35 ` Koen Kooi
2007-12-02 17:22 ` Richard Purdie
2007-12-02 19:13 ` Koen Kooi
2007-12-02 18:45 ` Marcin Juszkiewicz
2007-12-02 18:17 ` Paul Sokolovsky
2007-12-02 20:52 ` Rod Whitby
2007-12-03 15:21 ` Leon Woestenberg
2007-12-04 0:07 ` Rod Whitby
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=1196595074.6648.11.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=angstrom-distro-devel@linuxtogo.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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.