Kevin Ryde <[EMAIL PROTECTED]> writes: > I'd be inclined to make one radical change, and not worry about the > old stuff. Someone can still grab slib.scm from 1.6.4 or whatever > if they really need it, ie. don't want to update immediately.
I wouldn't be comfortable with that approach for a stable release. In general, I want to try and make sure that all of our stable releases have little or no affect on existing systems, aside from bug fixes. Unfortunately, it is true that the changes I'm planning here have the potential to break existing systems, but I'm willing to accept that, given the fairly trivial, one-line, workaround. (Of course, I'd still be happier if we didn't have to require affected people to change any code.) Also, I'm not positive, but I think some of the remaining bits in slib.scm may not have made it into an SLIB release yet. They will, but I'm not sure they have yet. With respect to 1.7, I believe I essentially agree with you. My current plan for 1.7 is to change slib.scm to more or less just read: (load-from-path "slib/guile.init") -- Rob Browning rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://lists.gnu.org/mailman/listinfo/guile-devel
