At 06:12 PM 7/28/2002, Justin Erenkrantz wrote: >On Sun, Jul 28, 2002 at 08:35:13PM +0200, Graham Leggett wrote: > > Justin Erenkrantz wrote: > > > > >In the past, people have suggested a CPAN/PEAR-approach where > > >modules are downloaded when needed. > > > > Modules in source form or binary form? > >Source. Binaries are too troublesome. -- justin
It would not be difficult to support binaries as well. Not only can you download modules from CPAN ... but also packages. E.g. it isn't terribly impossible to release the same sort of 'rollups' we've discussed before on the list. Start from a known good core package, and roll in the known good module versions. If several modules are fixed [or the core is fixed] for a set of bugs, and new good known tags are available, then a set of common modules, or a complete set of modules could be downloaded. Based on any of the common or complete packages, one could then create binaries. I don't know that module-by-module binary downloads make sense, since they all have to be tagged, are specific to a given core release, and possibly specific to given module releases as well [think of a DAV provider, which needs to be in sync with the core and dav/main srcs]. Bill
