Re: [racket-dev] Pre-Release Checklist for v6.1.1

2014-10-18 Thread Doug Williams
Done.

On Thu, Oct 16, 2014 at 7:13 AM, Ryan Culpepper  wrote:

> Checklist items for the v6.1.1 release
>   (using the v6.1.0.900 release candidate build)
>
> Search for your name to find relevant items, reply when you finish an
> item (please indicate which item/s is/are done).  Also, if you have any
> commits that should have been picked, make sure that the changes are in.
>
> Important: new builds are created without announcement, usually whenever
> I pick a few commits.  If you need to commit changes, please make sure
> you tell me to pick it into the release branch.
>
> --> Release candidates are at
> -->   http://pre-release.racket-lang.org
>
> Please use these installers (or source bundles) -- don't test from
> your own git clone (don't test the `master' branch by mistake!).  To
> get the tests, you can do this:
>
>   cd ...racket-root...
>   ./bin/raco pkg install -i main-distribution-test
>
> --
>
> * Matthew Flatt 
>   - Racket Tests
>   - Languages Tests
>   - GRacket Tests (Also check that `gracket -z' and `gracket-text' still
> works in Windows and Mac OS X)
>   - mzc --exe tests
>   - .plt-packing Tests
>   - Games Tests
>   - Unit Tests
>   - Syntax Color Tests
>   - R6RS Tests
>   - JPR's test suite
>   - Create an executable from a BSL program
>   - Run COM tests
>   - Embed-in-c test
>   - Try compiling with -funsigned-char
>   - Try compiling with TEST_ALTERNATE_TARGET_REGISTER
>   Updates:
>   - Racket Updates: update HISTORY
>   (updates should show v6.1.1 as the most current version)
>   - Update man pages in racket/man/man1: racket.1, gracket.1, raco.1
>   Email me to pick the changes when they're done, or tell me if there
>   are no such changes.
>
> * Robby Findler 
>   - DrRacket Tests
>   - Framework Tests
>   - Contracts Tests
>   - Games Tests
>   - Teachpacks Tests: image tests
>   - PLaneT Tests
>   - Redex Tests
>   Updates:
>   - DrRacket Updates: update HISTORY
>   - Redex Updates: update HISTORY
>   (updates should show v6.1.1 as the most current version)
>   - Ensure that previous version of DrRacket's preference files still
> starts up with new DrRacket
>   - Update man pages in racket/man/man1: drracket.1
>   Email me to pick the changes when they're done, or tell me if there
>   are no such changes.
>
> * John Clements 
>   - Stepper Tests
>   Updates:
>   - Stepper Updates: update HISTORY
>   (updates should show v6.1.1 as the most current version; email me
>   to pick the changes when they're done, or tell me if there are no such
>   changes.)
>
> * Sam Tobin-Hochstadt ,
>Vincent St-Amour 
>   - Match Tests
>   - Typed Racket Tests
>   - Typed Racket Updates: update HISTORY
>   (updates should show v6.1.1 as the most current version; email me
>   to pick the changes when they're done, or tell me if there are no such
>   changes.)
>
> * Matthias Felleisen 
>   - Teachpacks Tests: check that new teachpacks are addable
>   - Teachpack Docs: check teachpack docs in the bundles
>   - Try teaching-languages testing framework (check-expect)
>   Updates:
>   - Teachpack Updates: update HISTORY
>   (updates should show v6.1.1 as the most current version; email me
>   to pick the changes when they're done, or tell me if there are no such
>   changes.)
>
> * Ryan Culpepper 
>   - Macro Debugger Tests
>   - syntax-parse Tests
>   - RackUnit GUI Tests
>   - Data Tests
>   - DB Tests
>   - Rackunit Tests
>   - SRFI Tests
>
> * Jay McCarthy 
>   - Web Server Tests
>   - XML Tests
>   - HTML Tests
>   - PLAI Tests
>   - Racklog tests
>   - Datalog tests
>
> * Stevie Strickland 
>   - Unit Contract Tests
>   - Contract Region Tests
>   - Class Contract Tests
>
> * Stephen Chang 
>   - Lazy Racket Tests
>   - Lazy stepper tests
>
> * Eli Barzilay 
>   - Swindle Tests
>   - XREPL Tests
>   - Verify PL language
>   - Racket Tree: compare new distribution tree to previous one
>   - Run the unix installer tests
>   - Run zsh completions tests
> (". .../racket-completion.zsh; _racket --self-test")
>
> * Stephen Bloch 
>   - Picturing Programs Tests
>
> * Greg Cooper 
>   - FrTime Tests
>
> * Jon Rafkind 
>   Release tests for (one of the) linux releases:
>   - Test that the `racket' and `racket-textual' source releases
> compile fine (note that they're still called `plt' and `mz' at
> this stage).
>   - Test that the binary installers for both work, try each one in
> both normal and unix-style installation modes. (just ubuntu)
>   [Note: get the release candidates from the URL in this email. Use
>the 'static table' link to see a list of all tar files available]
>
> * Mike Sperber 
>   - DMdA Tests
>   - Stepper Tests
>   - Signature Tests
>
> * David Van Horn 
>   - EoPL Tests
>
> * Neil Toronto 
>   - Plot Tests
>   - Images Tests
>   - Inspect icons
>   - Math tests
>
> * Doug Williams 
>   - Additional Plot Tests
>
> * Shriram Krishnamurthi 
>   Tour: check the tour and generate a new o

Re: [racket-dev] Pre-Release Checklist for v6.1.1

2014-10-18 Thread Robby Findler
On Thu, Oct 16, 2014 at 8:13 AM, Ryan Culpepper  wrote:
> * Robby Findler 
>   - DrRacket Tests
>   - Framework Tests
>   - Contracts Tests
>   - Games Tests
>   - Teachpacks Tests: image tests
>   - PLaneT Tests
>   - Redex Tests

Done.

>   Updates:
>   - DrRacket Updates: update HISTORY
>   - Redex Updates: update HISTORY

Pushed.

>   (updates should show v6.1.1 as the most current version)
>   - Ensure that previous version of DrRacket's preference files still
> starts up with new DrRacket
>   - Update man pages in racket/man/man1: drracket.1
>   Email me to pick the changes when they're done, or tell me if there
>   are no such changes.

Done.

Robby
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] advice on the 6.x build system.

2014-10-18 Thread Matthew Flatt
At Fri, 17 Oct 2014 17:56:51 +0200, David Bremner wrote:
> Matthew Flatt  writes:
> 
> >
> > Meanwhile, I haven't answered your original question. Can you remind me
> > of the specific steps that I'd need to follow to try the script that
> > you sent before?
> 
> With your indulgence, I'll just answer this part now. I have re-included
> the Makefile as an attachment, since make is fussy about whitespace.
> 
> Save the attached file to e.g. /tmp/test.mk
> 
> In a recent checkout of the release branch, 
> 
> % make -f /tmp/test.mk build-indep-stamp
> 
> the resulting build of racket will be in test-dest, in the top level
> directory of racket. For me, test-dest/usr/bin only has racket and raco
> in it.

The problem is that `make install` works with a configuration whose
paths are based on DESTDIR, but as its final act it rewrites
"config.rktd" and other files to strip away DESTDIR. That rewrite tells
the later use of `raco pkg install` to put binaries in the DESTDIRless
path (i.e., "/usr/bin"), and so on. It's a kind of bad luck that `raco
pkg install` runs at all, since it could depend on the DESTDIRless pass
in any number of ways, such as an embedded path in a shared library.

If you really want to go this way, I could extend the makefile to let
you supply a command that runs before the path-fixup step of `make
install`. Then, your "test.mk" would look more like this:

build-arch-stamp: ${base_build_dir}/Makefile
$(MAKE) -C ${base_build_dir} 
$(MAKE) -C ${base_build_dir} DESTDIR=${destdir} install \
  FINAL_PREP_CMD="cd $(CURDIR) \
  && $(MAKE) RACKET="'"'"${PRERACKET}"'"'" \
 local-source-catalog \
  && ${PRERACKET} -N raco -l- \
  pkg install ${raco_args} \
  main-distribution racket-lib"
touch $@

_
  Racket Developers list:
  http://lists.racket-lang.org/dev


[racket-dev] package source as a Git repo

2014-10-18 Thread Matthew Flatt
The development version of the package manager now supports Git
repository references using "http[s]://" and sites other than GitHub.
That is, a package source can have the form

 git://host/[...]

for a host other than "github.com", and a source can have one of the
forms

 http://[...].git
 https://[...].git

which use the Git protocol over a "smart" HTTP(S) transport. In
particular, the "HTTPS" URL that appears on a GitHub repository page
will work directly as a package source.


Since generalized Git repository references are not supported in the
upcoming v6.1.1 release, it will be a while before you'll want to
publish package sources using the new forms. 

_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] Pre-Release Checklist for v6.1.1

2014-10-18 Thread Michael Sperber

Ryan Culpepper  writes:

> * Mike Sperber 
>   - DMdA Tests
>   - Stepper Tests
>   - Signature Tests

Done.

-- 
Regards,
Mike
_
  Racket Developers list:
  http://lists.racket-lang.org/dev