#1 Module/Plugin Installation Support

[Guillaume Desnoix]

I would like a support in VAInstall for module/plugin
support. The main application is for example packaged
with VAInstall. This application has optionnal modules
which should be packaged and installed by VAInstall
(same place, version check, ...). Eventually a list of
installed modules could be maintained by VAInstall.

[Anonymous]

Logged In: YES
user_id=179443

I'm not completely sure what you mean. Do you mean:

I have an application that I like user to install.
It has some core components, documentation, examples and sourcecode.

VAInstall show a dialog with a list of chooseable 'sub-packages' to install:
1. The core application , Required
2. Documentation, Optional
3. Examples, Optional
4. Sourcecode, Optional

This feature is very important!

We need to make a 'little' more complex filelist (because there could be dependencies between
sub-modules) and has to remember which sub-modules/sub-packages for uninstall.

The filelist then should have one more level. And that's why I think XML copuld be interesting
as a way to express the filelist.

[Guillaume Desnoix]

Logged In: YES
user_id=26290

It would be nice to have a modular installation (a set of
components which an user can choose - as you described). But
my request is different. I would like people to be able to
install _later_ some additional sub-packages. For example,
my app can use a scripting language which is not provided
with the default installation. This module can be downloaded
and installed later (and eventually uninstalled). VAInstall
would update the list and install the new component in the
same directory. To implement this feature, the current
fileset is enough but a new mode has to be created (i
guess).