From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: RPM vs IPK
Date: Mon, 21 Mar 2011 11:57:31 +0000 [thread overview]
Message-ID: <1300708651.30423.3434.camel@rex> (raw)
In-Reply-To: <4D86B0D2.2070004@mlbassoc.com>
On Sun, 2011-03-20 at 19:58 -0600, Gary Thomas wrote:
> I know that historically Poky has used 'ipk' as the primary packaging
> mechanism. It seems that now Poky/Yocto has move to 'rpm'. My distribution
> is still using ipk, but I'm happy to change, given a good argument.
>
> * Is there such [a good reason] to use rpm over ipk?
> * What are the pros and cons? I'm mostly interested in very resource limited
> deeply embedded systems which often only run from FLASH.
>
> Thanks for any comments
My advice is that for such a resource limited system, you're probably
best of sticking to ipk, particularly if you have it working already.
opkg:
* Has a smaller disk footprint
* Is generally faster than rpm
rpm+zypper:
* More of an industry standard
* Emphasises correctness and robustness over speed (e.g. number of
fsync calls)
* Has desktop/enterprise features
* Not optimised for size (e.g. uses c++)
I'd not say one was better than the other, they're just different and
suit different use cases.
Cheers,
Richard
next prev parent reply other threads:[~2011-03-21 11:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 1:58 RPM vs IPK Gary Thomas
2011-03-21 11:57 ` Richard Purdie [this message]
2011-03-21 14:02 ` Gary Thomas
2011-03-21 14:42 ` Richard Purdie
2011-03-21 16:33 ` Mark Hatle
2011-03-22 0:20 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2011-05-19 14:05 Gary Thomas
2011-05-19 14:17 ` Mark Hatle
2011-05-19 14:26 ` Gary Thomas
2011-05-19 15:28 ` Stewart, David C
2011-05-19 15:40 ` Gary Thomas
2010-10-29 21:33 Gary Thomas
2010-10-29 21:39 ` Gary Thomas
2010-10-30 6:17 ` Richard Purdie
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=1300708651.30423.3434.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.com \
--cc=poky@lists.pokylinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox