I'm still thinking that I'll keep my existing multi-collection packages as multi, to preserve compatibility with 5.3.4. Only because, although my packages don't have many users, I'll err on the side of their convenience.
But if someone else did want to change from multi to single: 1. Philosophical: Wouldn't this be bad to do without renaming the package, since the spirit of the package system versioning is, never break backward compatibility? Or, is it acceptable, now, since this is technically still in beta? 2. Practical: Would `raco pkg update' handle such a multi->single transform? Or should packagers instruct users to (a) remove and (b) install? I'm asking in case it would help to have the answer(s) ready for doc or FAQ purposes. On Sat, Jun 15, 2013 at 11:19 AM, Matthew Flatt <mfl...@cs.utah.edu> wrote: > At Fri, 14 Jun 2013 21:14:58 -0400, Greg Hendershott wrote: >> I just want to be clear what I need to do to >> keep compatibility with 5.3.4 for existing packages. If that means >> adding something to info.rkt to say, "yeah, I'm still multi", I may do >> that. > > Yes, that's exactly what will be required for a package to work with > both v5.3.4 and after the change: keep the package multi-collection, > and explicitly declare it as such by adding a line to "info.rkt". > > For the new "info.rkt" field, should it be > > (define multi-collection? #t) > > ? > _________________________ Racket Developers list: http://lists.racket-lang.org/dev
