Thomas Leonard wrote:
>> The OOo feed could most certainly use the download directly,
>> just that I didn't know how to write a custom archive phase ?
> Currently, you can't. There's no particular reason why we can't
> extract archives recursively, but I'm not sure it's very useful.
It even uses gzip on gzip, which is something of a waste of
resources (especially since it doesn't compress very well)
i.e. if you use a .tar.xz, instead of rpm or dep + tar.gz,
the resulting download is 127M rather than the current 147M)
The main "advantage" of doing one archive is that you can
bundle an installer application with it, so that people
used to setup.exe won't feel lost or have to learn to use
a package manager. Similarly, have the installer/application
update itself (with another bundled application) instead of
just using the package managers update feature to do that.
I'm sure that these package archives come from the equivalent
of 0export - but using rpm or dpkg instead of Zero Install...
(PBI is a similar project for BSD Ports, see http://pbidir.com)
All so that application installation can be as "good" as it
is on Windows, and so it all can continue to be done manually.
Then again, running the installer/update application can't
possibly be worse than having to use the terminal to do it:
> For example, if you use Zero Install to run OpenOffice Base (the
> database), it should only download the RPMs needed to run that (e.g.
> "base" and "core"). If you then run Writer, it should download the
> "writer" RPM but use the cached copy of "core".
> Perhaps we could host the extracted RPMs on sf.net? (Even under
> 0install.net if you want. I've added you to the project members list
> in any case.)
Perhaps, but if I wanted that - I *could* have just installed
the RPMs or DEBs from the current distro instead of using the
vendor packages, that they don't bother making any repo for ?
i.e. use yum or apt and an install, rather than rpm or dpkg.
Otherwise I would have to sort out all the dependencies and
set up PATHs for linking and runtime and all the other stuff
that the "soffice" launcher script is expecting to be there.
(there are 59 packages that make up the OOo installation...)
It's probably the *right* thing to do, but it's more work than
just extracting and wrapping the current "everything" tarball ?
And of course one needs to do this one time _for each language_,
there's 33 locales for OpenOffice.org and like 65 for Mozilla*.
But I'll try to fix my feeds to not abuse the cache directory,
maybe it can extract to something like /var/tmp/$USER instead ?
The RPMS are still the "source", having to extract (or install)
the packages before running them is more like a "side effect".