All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rod Whitby <rod@whitby.id.au>
To: openembedded-devel <openembedded-devel@openembedded.org>
Cc: angstrom-distro-devel <angstrom-distro-devel@linuxtogo.org>
Subject: RFC: Add ipkg to minimal image
Date: Sun, 02 Dec 2007 11:48:51 +1030	[thread overview]
Message-ID: <475207FB.8020405@whitby.id.au> (raw)

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).

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?

Does anyone object to me adding ipkg support to minimal-image?

FYI, minimal-image.rootfs.jffs2 for ixp4xx is 3.8M whereas
console-image.rootfs.jffs2 for ixp4xx is 7.1M

-- Rod



             reply	other threads:[~2007-12-02  1:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-02  1:18 Rod Whitby [this message]
2007-12-02  3:57 ` RFC: Add ipkg to minimal image 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
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=475207FB.8020405@whitby.id.au \
    --to=rod@whitby.id.au \
    --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.