Re: enhancing ipks

On Sun, May 20 '01 at 22:43, Carl Worth wrote:
> > While this would be a solution, we'd need a special "server" to do this.
> > And unpacking a ipkg file to get just the data.tar.gz puts unneeded load
> > onto the server.
> The server need not be that special. Simply have the two data.tar.gz
> and control.tar.gz pre-extracted from the .ipk on the server. This
> also eliminates the load problem. I imagine this as simply an
> alternate storage format on the server.
In this case we have to take special care not to put all the
data.tar.gz's and control.tar.gz's into the rsync you will soon offer
for familiar ;-), but provide an update script that extracts them from
the ipkg files. But (than) this would work.

> This is the reason I have been thinking of using systems such as stow
> or graft, [ ... ] In those systems each package is installed to its
> own subdirectory, (and symlinks are generated to make it appear to be
> installed in a common directory with all other packages).
> [ ... ]
> All this symlinking could have some negative overhead, but it's
> probably reasonable.
I don't mind a minimal overhead when loading programs, but we must take
care not to put all this symlinks into the JFF2 but into a ramfs. But
this (too) would work, and be pretty slick, you could also add an .menu
file or simmilar to add the menu entries.

I'll check the debian menu system for an inspiration.

Cu,
    Goetz.