[Buildroot] package management

[Buildroot] package management

[Xianghua Xiao]

will buildroot have opkg sometime soon?
thanks,
xianghua

[Buildroot] package management

[Thomas Petazzoni]

Hello,

On Fri, 13 May 2011 21:14:00 -0500
Xianghua Xiao <xiaoxianghua@gmail.com> wrote:

> will buildroot have opkg sometime soon?

Soon, quite certainly not. Someday, maybe. But there's a lot of work to
be done at the package infrastructure level to make this possible. It
is not as simple as one might initially think to add this kind of
features.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] package management

[Grant Edwards]

On 2011-05-14, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> On Fri, 13 May 2011 21:14:00 -0500
> Xianghua Xiao <xiaoxianghua@gmail.com> wrote:
>
>> will buildroot have opkg sometime soon?
>
> Soon, quite certainly not. Someday, maybe. But there's a lot of work to
> be done at the package infrastructure level to make this possible. It
> is not as simple as one might initially think to add this kind of
> features.

I'm curious about this.  I'm using ipkg and it works fine.  Opkg seems
to be based on (and very similar to) ipkg.  What is different about
opkg that makes it difficult?

-- 
Grant

[Buildroot] package management

[Thomas Petazzoni]

On Sat, 14 May 2011 13:49:07 +0000 (UTC)
Grant Edwards <grant.b.edwards@gmail.com> wrote:

> > Soon, quite certainly not. Someday, maybe. But there's a lot of
> > work to be done at the package infrastructure level to make this
> > possible. It is not as simple as one might initially think to add
> > this kind of features.
> 
> I'm curious about this.  I'm using ipkg and it works fine.  Opkg seems
> to be based on (and very similar to) ipkg.  What is different about
> opkg that makes it difficult?

Maybe I misunderstood Xianghua initial request. I thought he was asking
for Buildroot to generate ipkg/opkg packages, which Buildroot isn't
capable of doing at the moment. If he is asking about having the
opkg/ipkg-utils installed in a Buildroot system, then obviously it's
fairly easy.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] package management

[Grant Edwards]

On 2011-05-14, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> On Sat, 14 May 2011 13:49:07 +0000 (UTC)
> Grant Edwards <grant.b.edwards@gmail.com> wrote:
>
>> > Soon, quite certainly not. Someday, maybe. But there's a lot of
>> > work to be done at the package infrastructure level to make this
>> > possible. It is not as simple as one might initially think to add
>> > this kind of features.
>> 
>> I'm curious about this.  I'm using ipkg and it works fine.  Opkg seems
>> to be based on (and very similar to) ipkg.  What is different about
>> opkg that makes it difficult?
>
> Maybe I misunderstood Xianghua initial request.

Or perhaps I did.

> I thought he was asking for Buildroot to generate ipkg/opkg packages,
> which Buildroot isn't capable of doing at the moment.

Ah, he probably was.

> If he is asking about having the opkg/ipkg-utils installed in a
> Buildroot system, then obviously it's fairly easy.

That's what I'm doing with ipkg.  I have ipkg utilties enabled in my
buildroot system.  My "user" applications are built outside of
buildroot and packaged using ipkg.  Then I install them on the
buildroot target using ipkg.

-- 
Grant Edwards               grant.b.edwards        Yow! Now that I have my
                                  at               "APPLE", I comprehend COST
                              gmail.com            ACCOUNTING!!

[Buildroot] package management

[Xianghua Xiao]

On Sat, May 14, 2011 at 10:26 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> On Sat, 14 May 2011 13:49:07 +0000 (UTC)
> Grant Edwards <grant.b.edwards@gmail.com> wrote:
>
>> > Soon, quite certainly not. Someday, maybe. But there's a lot of
>> > work to be done at the package infrastructure level to make this
>> > possible. It is not as simple as one might initially think to add
>> > this kind of features.
>>
>> I'm curious about this. ?I'm using ipkg and it works fine. ?Opkg seems
>> to be based on (and very similar to) ipkg. ?What is different about
>> opkg that makes it difficult?
>
> Maybe I misunderstood Xianghua initial request. I thought he was asking
> for Buildroot to generate ipkg/opkg packages, which Buildroot isn't
> capable of doing at the moment. If he is asking about having the
> opkg/ipkg-utils installed in a Buildroot system, then obviously it's
> fairly easy.
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>

I never used ipkg/opkg on buildroot though I saw the package itself
there, can you do 'ipkg update/remove/install' reliably? i think it's
either fully-ipkg aware, or nothing, as using ipkg directly(acting
like a 'make install') may break things easily unless it's a
fully-ipkg-aware distribution.

Thanks,

[Buildroot] package management

[Grant Edwards]

On 2011-05-14, Xianghua Xiao <xiaoxianghua@gmail.com> wrote:

>>> I'm curious about this. I'm using ipkg and it works fine. Opkg seems
>>> to be based on (and very similar to) ipkg. What is different about
>>> opkg that makes it difficult?
>>
>> Maybe I misunderstood Xianghua initial request. I thought he was
>> asking for Buildroot to generate ipkg/opkg packages, which Buildroot
>> isn't capable of doing at the moment. If he is asking about having
>> the opkg/ipkg-utils installed in a Buildroot system, then obviously
>> it's fairly easy.
>
> I never used ipkg/opkg on buildroot though I saw the package itself
> there, can you do 'ipkg update/remove/install' reliably?

Yes it works fine for all of the programs I've packaged.

> i think it's either fully-ipkg aware, or nothing, as using ipkg
> directly (acting like a 'make install') may break things easily
> unless it's a fully-ipkg-aware distribution.

Sorry, I don't know what that last sentence means.  I'll try again to
explain what is supported.

Buildroot does not produce .ipk files/packages.

Buildroot can build and install the ipackage utilities in the target
image.  Those ipackage utilties work fine on the target.  I use them
to install, update, and uninstall .ipk files I build outside of
buildroot.

-- 
Grant

[Buildroot] Package Management

[John Tobias]

Hello all,

My package management support is working in generic-package,
pkg-autotools, pkg-cmake. By default, if you compile any libraries, it
will create a package file (.pkg) with or without modifying the .mk
file of the library, except for generic-package. I will provide a
patch file sometimes next week if you guys are interested to try it...

Right now, if I compile the busybox for example, I have to add the
function BUSYBOX_CREATE_PACKAGE_CMDS definition in the .mk file of the
busybox.

define BUSYBOX_CREATE_PACKAGE_CMDS

endif


So, in my pkg-generic.mk I added the following:

# Create package
$(BUILD_DIR)/%/.stamp_create_package:
@$(call MESSAGE,"Creating package")
$($(PKG)_CREATE_PACKAGE_CMDS)
$(foreach hook,$($(PKG)_POST_CREATE_PACKAGE_HOOKS),$(call $(hook))$(sep))
$(Q)touch $@


I need to check if the $(PKG)_CREATE_PACKAGE_CMDS exist or not in the
current building library, so I did the following:

# Create package
$(BUILD_DIR)/%/.stamp_create_package:
ifdef $(PKG)_CREATE_PACKAGE_CMDS
@$(call MESSAGE,"Creating package")
$($(PKG)_CREATE_PACKAGE_CMDS)
$(foreach hook,$($(PKG)_POST_CREATE_PACKAGE_HOOKS),$(call $(hook))$(sep))
endif
$(Q)touch $@


But, calling "ifdef $(PKG)_CREATE_PACKAGE_CMDS" to filter if the said
function is exist or not.

So my question is, how to check if the $(PKG)_CREATE_PACKAGE_CMDS is
exist or not?.

Regards,

john