opkg vs dpkg/rpm

opkg vs dpkg/rpm

[l.bolognini]

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

Re: opkg vs dpkg/rpm

[Chris Larson]

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"

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

Re: opkg vs dpkg/rpm

[Denys Dmytriyenko]

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

Re: opkg vs dpkg/rpm

[Graham Gower]

On 2 September 2010 04:55, Denys Dmytriyenko <denis@denix.org> wrote:
> 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

It would be trivial to write a script to convert the package database
from one package manager's format to another. Surely someone has
already done this?

-Graham

Re: opkg vs dpkg/rpm

[Tom Rini]

Graham Gower wrote:
> On 2 September 2010 04:55, Denys Dmytriyenko <denis@denix.org> wrote:
>> 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
> 
> It would be trivial to write a script to convert the package database
> from one package manager's format to another. Surely someone has
> already done this?

The big issue is converting the package files, although I suspect alien 
could be used here since it does .debs and ipk is a stripped down deb it 
might work, or might not, but could be made to work.

The bigger problem however is it's unclear if rpm or deb support is 
currently unbitrotten enough to work (deb stuff frequently has the 
problem that upstream upgraded, and we did not, so sources are gone).

-- 
Tom Rini
Mentor Graphics Corporation