Michael Homer <mich...@...> writes: > I have seen > your 2.3 patch linked from the tracker and need to think on it a > little more - it looks right, but I think actual 2.3 compatibility has > long since been given up as a goal* and I don't really want to commit > to avoiding the new features everywhere.
In lieu of factoring out all of the CreateRootlessEnvironment dependencies and thereby enforcing 2.3 compatibility only on a small subset, it is probably sufficient to make the installer work with and depend on a specific version of Scripts with this patch and then bootstrap to the required version of Python (which will be straightforward once automatic determination of the installed version is properly listed in Dependencies.blacklist or by touching the appropriate Program/* directory. (I have been doing the later and it has been working well. The only advantage I see with a versioned Dependencies.blacklist is that it gives a single file for the user to modify if the update the host system, but this should probably be automated anyway.) Quick question: What would be the appropriate set of steps to re-establish a Rootless installation if the user updates the host system? Is there a unified way to trigger a system-wide dependency recheck, bringing all software up to date with the modified dependencies and rebuilding only where needed? Thanks, Michael. _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
