Hi all - <br><br>I am pleased to announce the release of BZLIB/PLANET.plt - a planet proxy/repository. It is available via planet, of course. <br><br>With it, you can run your own local planet proxy/repository, so you can do the following:<br>
<ul><li>shield yourself from the occasional central repository outage <br></li><li>run labs without internet connections </li><li>test-run your planet package installs, without having to upload to the central repository and hence potentially create a bad version and eat up the planet version number <br>
</li><li>distribute private code that you do not want to make publicly available via your planet proxy </li><li>setting up public mirrors of the central repository to help alleviate bandwidth constraints (future todo) <br>
</li></ul>You can find the usage here - <a href="http://weblambda.blogspot.com/2010/01/bzlibplanetplt-local-planet.html">http://weblambda.blogspot.com/2010/01/bzlibplanetplt-local-planet.html</a>. <br><br>Let me know if there are any questions - comments/feedbacks welcome.<br>
<br>Cheers,<br>yc<br><br><div class="gmail_quote">On Tue, Jan 12, 2010 at 11:52 AM, Robby Findler <span dir="ltr"><<a href="mailto:robby@eecs.northwestern.edu" target="_blank">robby@eecs.northwestern.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>On Mon, Jan 11, 2010 at 11:42 PM, YC <<a href="mailto:yinso.chen@gmail.com" target="_blank">yinso.chen@gmail.com</a>> wrote:<br>
> Hi all,<br>
><br>
> I am getting close to have a working implementation of a planet proxy, and I<br>
> can make a release once I can resolve/implement against the following<br>
> questions:<br>
><br>
> 1 - does the planet system make use of the 'required-core-version'? I was<br>
> able to install a package marked for 4.1 (via the planet edit metadata page)<br>
> from PLT4.0. What should the behavior be in such case?<br>
<br>
</div>The server uses that to decide which package to point a client to. You<br>
can say "planet url ..." from your client to see this in action. That<br>
is, if you use "planet url" from version 4.0 on a package marked for<br>
4.1, you won't get that one back.<br>
<div><br>
> 2 - also - does the planet system make use of the 'repositories' value from<br>
> info.ss?<br>
<br>
</div>Yes. It is used as the above, I believe, but also used to control what<br>
shows up on the front page (see the link at the top next to "view<br>
packages" at <a href="http://planet.plt-scheme.org/" target="_blank">http://planet.plt-scheme.org/</a>).<br>
<div><br>
> 3 - the package-source url (<a href="http://planet.plt-scheme.org/package-source/" target="_blank">http://planet.plt-scheme.org/package-source/</a>)<br>
> used to be visible with package directories but now it is forbidden. This<br>
> page provides a point for a crawler to mirror the packages. Can we make it<br>
> (and the children path) visible again?<br>
<br>
</div>I think I've fixed that, thanks.<br>
<font color="#888888"><br>
Robby<br>
</font></blockquote></div><br>