From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: opkg vs dpkg/rpm
Date: Wed, 01 Sep 2010 15:25:10 -0400 [thread overview]
Message-ID: <20100901192510.GA24544@denix.org> (raw)
In-Reply-To: <AANLkTi=U33a2xMK4SWWmF8c6hPi18vnedSaoTARuMwPn@mail.gmail.com>
On Wed, Sep 01, 2010 at 07:43:38AM -0700, Chris Larson wrote:
> In addition to package writing, there's the IMAGE_PKGTYPE varaible which
> controls which of the rootfs_<pkgtype> bbclasses is used to construct the
> root filesystem. You can inherit multiple packaging formats, resulting in
> multiple formats being emitted, but one has to be selected specifically for
> the filesystem. If you only inherit one packaging class (i.e. package_ipk)
> it will automatically set the image packaging type to match. So, to switch:
>
> 1) INHERIT += "package_rpm"
> 2) IMAGE_PKGTYPE = "rpm"
Just a small clarification for Chris' excelent explanation - the change of the
above variables will require a complete rebuild/repackage of all the packages
and the filesystem image. And it's not possible to make the switch for an
existing image or add another package manager to an existing image w/o losing
the database of installed packages...
--
Denys
> On Wed, Sep 1, 2010 at 6:57 AM, l.bolognini@tiscali.it <
> l.bolognini@tiscali.it> wrote:
>
> > Hi all,
> > I'm working on a beagleboard.
> > I'm wondering if there is a
> > quick
> > way to change package manager from opkg to dpkg or to rpm, both
> > on the
> > host and on the target.
> > I think that including dpkg package in,
> > for
> > example, arago-console-image is not enough because all packages
> > are
> > built with ipkg/opkg.
> > Moreover the directory /usr/lib/opkg/info
> > with
> > all postinst/prerm scripts could not be used anymore.
> >
> > I report a
> > small
> > extract from openembedded manual:
> > "The package_write task is
> >
> > responsible for taking each packages subdirectory and creating any
> >
> > actual
> > installation package, such as .ipk, .deb or .rpm. Currently .
> > ipk
> > is the only fully supported packing
> > format although .deb packages
> > are
> > being actively worked on."
> >
> > Has anyone tried a .deb or .rpm based
> >
> > rootfs (built with oe/bitbake) on beagleboard or in another target?
> >
> >
> >
> > Thanks for your attention,
> > best regards,
> > Luca
> >
> >
> > Risparmia con Tutto Incluso Light: telefono + adsl 8 mega a soli 19,95 ??? al
> > mese per un anno! SCONTO DI 120 EURO!
> > http://abbonati.tiscali.it/telefono-adsl/prodotti/tc/tuttoincluso_light/?WT.mc_id=01fw
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
>
>
>
> --
> Christopher Larson
> clarson at kergoth dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2010-09-01 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 13:57 opkg vs dpkg/rpm l.bolognini
2010-09-01 14:43 ` Chris Larson
2010-09-01 19:25 ` Denys Dmytriyenko [this message]
2010-09-01 22:35 ` Graham Gower
2010-09-01 22:44 ` Tom Rini
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=20100901192510.GA24544@denix.org \
--to=denis@denix.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.