[racket-dev] PLaneT(2): Single vs multi-collection packages
I vote for this change.
I'm happy to change my packages (which make more sense as
single-collection packages anyway).
If I understand correctly, this would also have the advantage of making
a lot of github repositories (including most of mine) installable as
packages automatically, no change required. That sounds like a huge win
to me.
Vincent
At Fri, 14 Jun 2013 07:07:26 -0700,
Matthew Flatt wrote:
>
> I think more people need to speak up on this question --- particularly
> authors of existing packages, since the current proposal necessitates
> an update to each existing package.
>
> The proposal is to make single-package collections the default:
>
> * If a directory used as a package has no "info.rkt" file, then it is
> treated as a single-collection package.
>
> The single collection's name is the same as the package name (which
> tends to be the directory name, but it depends on how you install
> the package).
>
> * If a directory used as a package has an "info.rkt" file, but
> "info.rkt" doesn't explicitly say that the package is
> multi-collection, then it's still a single-collection package.
>
> The "info.rkt" file might supply a name for the single collection,
> instead of leaving it to the package name; supplying a name would be
> a requirement for ring-0 packages.
>
> For each existing package, the author would need to add a line to the
> package's "info.rkt" to indicate that it is a multi-collection package
> (or change the layout to single-collection mode, with the caveat that
> the package won't work with v5.3.4).
>
> Any more votes for/against?
>
> _________________________
> Racket Developers list:
> http://lists.racket-lang.org/dev