Skip to contentSkip to conversation

is there any reason to use .ipk packaging if devs are using ubuntu?

DISCUSSION Robert P. J. Day 3 participants 6 messages Mar 23, 2024

lore
Share & tools
lore
#0 lore raw

yet another sophomoric question but i have inherited (and am
babysitting) a fairly extensive OE/YP build system that, for the most part, works but i noticed early on that it selects ipk for the package format.

now, given that there is no package management installed in the
images, i guess it really makes no difference what the package format is, but it just seems unnatural to use ipk given that the corp-approved linux development system is ubuntu.

is there any compelling argument for this? i suspect i could change
the packaging format and the developers would not even notice.

rday

#1 lore raw

Packaging format of the host distribution and packaging format used by yocto have no relation even if there is package management on real targets. Why is there an assumption that matching them is going to help something?

If anything, making them match might prompt misguided attempts to install Ubuntu packages in yocto systems and frustration at not being able to make it work.

Alex

Quoted 27 lines · Robert P. J. Day

yet another sophomoric question but i have inherited (and am
babysitting) a fairly extensive OE/YP build system that, for the most part, works but i noticed early on that it selects ipk for the package format.

now, given that there is no package management installed in the
images, i guess it really makes no difference what the package format is, but it just seems unnatural to use ipk given that the corp-approved linux development system is ubuntu.

is there any compelling argument for this? i suspect i could change
the packaging format and the developers would not even notice.

rday

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#197458):
https://lists.openembedded.org/g/openembedded-core/message/197458
Mute This Topic: https://lists.openembedded.org/mt/105106419/1686489
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#2 lore raw
Quoted 8 lines · Alexander Kanavin

Packaging format of the host distribution and packaging format used by yocto have no relation even if there is package management on real targets. Why is there an assumption that matching them is going to help something?

If anything, making them match might prompt misguided attempts to install Ubuntu packages in yocto systems and frustration at not being able to make it work.

all of this being accurate, the one advantage i can see is that, if
developers are familiar with deb package management on their ubuntu dev systems, then they would be familiar with having package management on their target systems (provided, as you say, they understand that they should work only with YP-generated packages).

rday

#3 lore raw
Quoted 5 lines · Robert P. J. Day

all of this being accurate, the one advantage i can see is that, if
developers are familiar with deb package management on their ubuntu dev systems, then they would be familiar with having package management on their target systems (provided, as you say, they understand that they should work only with YP-generated packages).

Nah, I don't see that familiarity helping anything. Reading output of opkg and finding out that you need to issue 'opkg install' takes 10 seconds. That's such a minor hurdle compared to learning yocto in general (especially when to do when bitbake ends with an error) that I'd say any time saved there is statistical noise.

Alex

#4 lore raw
Quoted 7 lines · Alexander Kanavin
Quoted 5 lines · Robert P. J. Day

all of this being accurate, the one advantage i can see is that, if
developers are familiar with deb package management on their ubuntu dev systems, then they would be familiar with having package management on their target systems (provided, as you say, they understand that they should work only with YP-generated packages).

Quoted 5 lines

Nah, I don't see that familiarity helping anything. Reading output of opkg and finding out that you need to issue 'opkg install' takes 10 seconds. That's such a minor hurdle compared to learning yocto in general (especially when to do when bitbake ends with an error) that I'd say any time saved there is statistical noise.

ok, that's reasonable. thanks.

rday

#5 lore raw
In reply to Robert P. J. Day
Quoted 12 lines · Robert P. J. Day
Quoted 8 lines · Alexander Kanavin

Packaging format of the host distribution and packaging format used by yocto have no relation even if there is package management on real targets. Why is there an assumption that matching them is going to help something?

If anything, making them match might prompt misguided attempts to install Ubuntu packages in yocto systems and frustration at not being able to make it work.

Quoted 6 lines

all of this being accurate, the one advantage i can see is that, if
developers are familiar with deb package management on their ubuntu dev systems, then they would be familiar with having package management on their target systems (provided, as you say, they understand that they should work only with YP-generated packages).

while ipk/deb/rpm are well supported in OE, rpm is defaults for poky reference distribution and ipk is default for nodistro if you were to use just oe-core, on yocto autobuilders, defaults poky configurations are tested extensively, so you might find a bit of better help if something goes wrong with rpm and its reproducible
on AB or indirectly you may build upon the testing that's happening on AB if you used rpm, having said that YP AB is also starting to test ipk backend and we did figure out a nasty lock/race condition in opkg, which has always been there so such issues would be less although not down to zero for you if you used more tested profiles.

downside is as Alex mentioned, construing yocto rpms/debs to be valid for other hosts
using same packaging backends, that's going to be a constant battle to keep your team
to be taught as new folks come on board etc.

If your workflows do involve package managers, then opkg is definitely lightweight and
easier setup for dev work.

Quoted 10 lines

rday

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#197461): https://lists.openembedded.org/g/openembedded-core/message/197461
Mute This Topic: https://lists.openembedded.org/mt/105106419/1997914
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-