Seems to me your schema is amenable to suffer heavy (if not fatal) blows from being unable to access the client per installation. (Unless, that is, your only targes are only, say, win32 machines with asperl 5.6.1 630, or a similarly tightly focused group)
I would expect it to be blocking for Xs stuff, but I think I remember many more libraries that refused to "make" if some crucial dependencies were missing...
So it looks to me that you'd be better off doing binary distributions - à la PPM - of the packages you need AND install those. Then whatever assumption you are making on the target client will be explicited in the architecture of the package.
Cheers,
alf
In reply to Re: Installing Modules through Web Interface?
by alien_life_form
in thread Installing Modules through Web Interface?
by Flame
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |