[racket] deprecating planet version using para. in planet description?

From: Neil Van Dyke (neil at neilvandyke.org)
Date: Fri Dec 6 02:21:55 EST 2013

Robby Findler wrote at 12/05/2013 04:02 PM:
> You could release a new planet version that required the pkg version 
> (this works especially well when the pkg is in the main-distribution 
> tho). I recommend a core version dependency in that case tho.

For this approach, would one need the reference to a new-package-system 
package to satisfy in perpetuity the guarantees of the PLaneT package's 
version numbers?  The first guarantee I mean is that a particular 
absolute version number spec always gets the same immediate code.  The 
second guarantee is of backward compatibility within the same major 
version.  Neither of these guarantees is always satisfied perfectly 
within the current PLaneT implementation, but I think any PLaneT package 
that is changed to be a wrapper for a new-package-system package should 
honor the guarantees to the extent that the non-wrapper package would've.

> You could also remove it from both planet repositories to just hide it 
> from planet depending on your desire to support older versions of racket.

Wouldn't that break all code that has a direct or indirect dependency on 
any version of that PLaneT package?

> On Thursday, December 5, 2013, John Clements wrote:
>     It looks to me like the easiest way to mark a PLaneT version of
>     some code as deprecated in favor of a package version (as e.g.
>     rsound) is to add a paragraph to the description metadata on the
>     PLaneT website.  I've done this for a few of my packages, but as I
>     don't see anyone else doing it, I wanted to check and see whether
>     there was general agreement on a different mechanism.

To mark a PLaneT package as deprecated, I would release a new minor 
version that puts a note about the deprecation as the first 
sentence/paragraph of the documentation.

Also noting the deprecation in the package metadata that shows up in 
package lists on the PLaneT site might save some people a little time. 
  If I did that, it would be in addition to the note in the documentation.

Neil V.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20131206/68148052/attachment.html>

Posted on the users mailing list.