[plt-scheme] Requiring absolute path

From: Neil Van Dyke (neil at neilvandyke.org)
Date: Mon Jun 15 17:21:55 EDT 2009

Neil Van Dyke wrote at 06/15/2009 05:12 PM:
> Paulo J. Matos wrote at 06/15/2009 04:59 PM:
>> maybe i am missing something but what do you mean by a planet 
>> development link?
> Courtesy of Google: 
> http://docs.plt-scheme.org/planet/Developing_Packages_for_PLaneT.html#(part._devlinks) 

For example, my "~/scheme/Makefile" at the moment includes the production:

    @echo ""
    planet unlink neil randtok.plt          1 0
    @echo ""
    planet link neil testeez.plt          1 3 ~/scheme/testeez
    planet link neil csv.plt              1 6 ~/scheme/csv
    planet link neil postnet.plt          1 1 ~/scheme/postnet
    planet link neil urlskip.plt          1 1 ~/scheme/urlskip
    planet link neil bigtime.plt          1 0 ~/scheme/bigtime
    planet link neil html-parse.plt       1 0 ~/scheme/html-parse
    planet link neil html-template.plt    1 0 ~/scheme/html-template
    planet link neil html-write.plt       1 0 ~/scheme/html-write
    planet link neil scgi.plt             1 0 ~/scheme/scgi
    planet link neil shtml.plt            1 0 ~/scheme/shtml
    planet link neil xexp.plt            1 0 ~/scheme/xexp
    @echo ""
    planet show
    @echo ""

Whenever I start modifying a package's source, in anticipation of a new 
PLaneT version, I add a "planet link" for that, giving the anticipated 
new PLaneT version number.  As I release versions of PLaneT packages, I 
change the corresponding "planet link" to a "planet unlink".  Sometime 
later, I remove the "planet unlink"s, once they've probably run on all 
the systems that need them (which, at the moment, is just my laptop).

This is a stopgap solution, until I get time to automate it based on 
information that is already embedded in my source files.


Posted on the users mailing list.