Vagrant Cascadian <vagr...@debian.org> writes: > It seems like simply providing the binaries with the versioned links > would be sufficient, since guile-2.2-dev conflicts/provides > libguile-dev, guile-2.0-dev and guile-2.2-dev can't be installed at the > same time. > > I guess it's possible the alternative for "guile" could be out of sync > with the installed guile-2.2-dev binaries, although the newer versions > have higher alternative default priority... > > The configure scripts seem to prefer the versioned binaries anyways...
Yep -- I'm not sure yet, but I may lean toward providing: bin/guile -> ./guile-2.2 # or whatever the selected alternative is bin/guild -> ./guild-2.2 # or whatever the selected alternative is ... And then make sure that guild-X.Y, etc. refer specifically to guile-X.Y (in, for example their #! lines), which I don't think they do right now. In the longer run, I'd like to match as much as possible what upstream does. We've supported multiple versions for longer, but I suspect upstream's approach is probably better (and more complete) than ours. (That and of course it's always better not to differ unless we need to.) Right now I'm poking around to see how where we might be headed eventually compares to what's feasible to do at the moment (given guile-2.0 and given the freeze). Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
