From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Creating Rootfs images without packages
Date: Thu, 13 Oct 2011 10:26:22 +0100 [thread overview]
Message-ID: <1318497983.14199.54.camel@phil-desktop> (raw)
In-Reply-To: <CAObi9r9=55i4W686VfCv-TGSChsrewu7zSGUsPZC2PbA3x3zbQ@mail.gmail.com>
On Wed, 2011-10-12 at 15:22 +0300, mgundes wrote:
> I think one of the big issue with OE is build time. It does everything
> for you, so that it takes too much times. I want to minimize build time and
> realized that OE creates ipkgs for almost every package. If there is a way
> to prevent creation of ipkgs it would be really good for me. In my opinion,
> it would be fine for other people too since usually rootfs directory is
> enough and ipkgs are not frequently used directly by developers.
If you want to eliminate ipk specifically then there is no problem: you
can select package_rpm or package_tar or package_deb instead.
If you want to eliminate the whole packaging step then this is rather
more tricky and it's not really obvious that this would buy much. Do
you have a proposal for how rootfs construction could be done in that
case?
p.
next prev parent reply other threads:[~2011-10-13 9:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 12:22 Creating Rootfs images without packages mgundes
2011-10-12 12:34 ` Gary Thomas
2011-10-12 13:10 ` mgundes
2011-10-12 13:21 ` Gary Thomas
2011-10-12 13:47 ` mgundes
2011-10-12 15:29 ` Chris Larson
2011-10-12 20:46 ` dashesy
2011-10-12 20:50 ` Khem Raj
2011-10-13 7:30 ` mgundes
2011-10-13 0:37 ` Ulf Samuelsson
2011-10-13 7:22 ` mgundes
2011-10-13 9:26 ` Phil Blundell [this message]
2011-10-13 11:07 ` mgundes
2011-10-14 0:05 ` Khem Raj
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=1318497983.14199.54.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-devel@lists.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.