On Mon, Jul 6, 2009 at 12:18 AM, Reinout Heeck<[email protected]> wrote: > Load (more precisely: use -- we might not be able to load it) a / > specific/ version of the Squeak tool, and then apply a separate (Pharo- > maintained) set of patches to make it Pharo compliant. > Define a process to specify how bug fixes are to be pushed upstream, > and how enhancements are pulled downstream -- reassessing the Pharo > patches each time a new version is pulled downstream.
This is something that works very well in Linux and I think we could use it. What we need to make this happen: 1) a repository of patched packages that can be easily loaded inside user images 2) a repository of patches that can be applied to tools in order to make them compatible with Pharo 3) a database which associates a package with a list of ordered patches to apply on it 4) a tool to populate the first repository with automatically created packages containing the patches. That tool should be able to apply patches without even load the package in the image (because there might be undefined references or overrides in non-existing classes...) What we have: 1) any Monticello repository would do (e.g., SqueakSource) 2) any ftp/http directory would do (like we do with the current update stream 'pharo.gforge.inria.fr') 3) it could be a directory per package (named with the name of the package) containing all patches for that package (named with a number indicating the order of patches) 4) that one should be written. Possible steps: unzipping the mcz, applying the patch to the source, creating a new mcz, pushing that mcz to the repository 1). What do you think? -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
