<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Robby Findler wrote at 12/05/2013 04:02 PM:
<blockquote
cite="mid:CAL3TdOPpw6=T=ZaRevWo7XxOUtJMj_VnrPw7EsXrgDiuotnfhg@mail.gmail.com"
type="cite">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.</blockquote>
<br>
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.<br>
<br>
<blockquote
cite="mid:CAL3TdOPpw6=T=ZaRevWo7XxOUtJMj_VnrPw7EsXrgDiuotnfhg@mail.gmail.com"
type="cite">
<div><br>
</div>
<div>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. </div>
</blockquote>
<br>
Wouldn't that break all code that has a direct or indirect dependency
on any version of that PLaneT package?<br>
<br>
<blockquote
cite="mid:CAL3TdOPpw6=T=ZaRevWo7XxOUtJMj_VnrPw7EsXrgDiuotnfhg@mail.gmail.com"
type="cite">
<div>On Thursday, December 5, 2013, John Clements wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">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.<br>
<br>
</blockquote>
</div>
</blockquote>
<br>
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.<br>
<br>
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.<br>
<br>
Neil V.<br>
<br>
</body>
</html>