Hello,

I have been hacking on the opkg solution, and reading all the ptxdist
scripts, whewww.
However, there are a few questions i had.

1. When ptxdist "uses" ipkg, it seems that the usage is in regards to when the
target is deployed. That is, it is not used, for example, with a
library being installed
to sysroot-target. The ipkg is created, but not used to install
locally (if that is the
correct term). The contents of the packages/package-xyz are copied to the rootfs
and host/target sysroot.

2. If the above assumption is somewhat correct, then would it be a TODO to use
opkg to install/uninstall to both sysroot-target, root, and
sysroot-host? This would eliminate
the need for the /usr/bin/install for the files, and a different view
of the state of a
package.

So, following each package being built, the ipk would be created, and
the Packages.gz
be updated (i thought it could be in platform-b/{host,target}-opkg/ ,
where also the
.conf files be stored, or a global one with targets

ex:   host-sysroot, target-sysroot, root

3. Right now, opkg does not have the capability to generate/update the package
index, or build ipk files. So, ipk would still be needed for this. The
opkg manager
would be a drop in to install, remove packages.

So... Was this the general idea? Comments, Encouragements :) ?

Cheers,
Ryan


On 24 September 2010 13:54, Robert Schwebel <[email protected]> wrote:
> On Fri, Sep 24, 2010 at 01:40:08PM +0200, Ryan Raasch wrote:
>> Was there a need to implement a more ipkg/dpkg implementation for
>> avoiding copying files from sysroot(i think it was there) to the
>> destination?
>>
>> I have some time, so i thought i would give it a whirl but i can't
>> quite  remember/figure out how ptxdist uses/doesn't ipkg. And where a
>> package  manager was needed to be used in the system.
>
> We currently use ipkg but would like to move to opkg in the future,
> parts of that have already started, my latest experiments are in
> http://git.pengutronix.de/?p=rsc/ptxdist;a=shortlog;h=refs/heads/rsc-work
>
> Marc has started to generalize the package generation (search for xpkg),
> but the work hasn't been finished and we are short of time recently.
>
> So if you want to give it a try, I'd be interested in patches which let
> us replace ipkg by opkg.
>
> Compared to deb, it doesn't need the complete database, which needs a
> lot of space on the target. However, extending ptxdist towards
> supporting deb in addition to opkg would be an option.
>
> Unsolved problems:
>
> - generating packet dependencies out of .in SELECT statements
> - inventing a concept for compile-time vs. runtime dependencies (think
>  of static libraries)
> - inventing a strategy when packet revisions have to be increased and if
>  we could get good (semi)automatisms for that.
>
> rsc
> --
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
>

-- 
ptxdist mailing list
[email protected]

Reply via email to