Re: [racket-dev] Pre-Release Checklist for v5.3.6
> * 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] > done _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Pre-Release Checklist for v5.3.6
On Mon, Jul 22, 2013 at 2:13 PM, Ryan Culpepper wrote: > > * 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 v5.3.6 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; no changes. Robby _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] `#%declare' and cross-phase persistent modules
The build completes successfully now. Thanks. On Mon, Jul 22, 2013 at 5:33 PM, Matthew Flatt wrote: > I'm seeing that in a fresh build. (Didn't see it before, because I had > mangled my build.) > > I'll push a repair shortly. > > At Mon, 22 Jul 2013 17:14:49 -0400, Stephen Chang wrote: >> When compiling a fresh git head clone, I still get some cross-phase >> persistence errors (see below). Is this my fault, or are some packages >> still missing the declaration? >> >> >> raco setup: --- checking package dependencies --- >> raco setup: >> raco setup: error: during making for >> /errortrace-doc/errortrace/scribblings >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /errortrace-lib/errortrace >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /errortrace-lib/errortrace >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /errortrace-lib/errortrace >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /errortrace-lib/errortrace >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /errortrace-lib/errortrace >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /errortrace-lib/errortrace/lang >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /algol60 >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /drracket/drscheme >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /drracket/drracket >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /drracket/drracket/private >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /drracket/scribble/tools >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /drracket/scribblings/tools >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /drracket/scribblings/tools >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /drracket/scribblings/tools >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /drracket/scribblings/drracket >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /drracket/drracket/private >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /drracket/scribblings/drracket >> raco setup: module: does not satisfy cross-phase persistent grammar >> raco setup: >> raco setup: error: during making for /drracket/drracket/private >> raco setup: module: does not satisfy cross-phase persistent grammar >> >> On Mon, Jul 22, 2013 at 12:18 PM, Matthew Flatt wrote: >> > As of v5.90.0.2 (pending), to declare a cross-phase persistent module, >> > the module body must include >> > >> > (#%declare #:cross-phase-persistent) >> > >> > If the module declaration fails to meet the syntactic and import >> > constraints of a cross-phase persistent module, then a syntax error is >> > reported. >> > >> > This change is backward-incompatible in two ways: >> > >> > * Module declarations that are intended as cross-phase persistent >> >won't be, anymore, until a `#%declare' form is added. >> > >> >I think cross-phase persistence is new enough --- and the old, quiet >> >inference of persistence is sufficiently distressing --- that this >> >won't be much of an issue. >> > >> > * The grammar of fully-expanded modules now includes `#%declare' >> >forms. >> > >> >Programs that process fully-expanded modules are not common, but I >> >expect that they exist outside of the main distribution. Those >> >programs will need to be updated. Meanwhile, they won't break until >> >they see a module that has a `#%declare' form, which won't happen >> >often (at least for the near future). >> > >> > Although `#:cross-phase-persistent' is the only keyword recognized by >> > `#%declare' initially, we'll add more. One possibility is a declaration >> > that corresponds to `compile-enforce-module-constants'. >> > >> > I named the form `#%declare' instead of `declare' to avoid conflicts, >> > and also becau
Re: [racket-dev] Pre-Release Checklist for v5.3.6
At Mon, 22 Jul 2013 15:13:28 -0400, Ryan Culpepper wrote: > > Checklist items for the v5.3.6 release >(using the v5.3.5.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.racket-lang.org/release/installers The "Linux/i386/Ubuntu Precise" installer is 64 bits, which is wrong. > * Sam Tobin-Hochstadt , > Vincent St-Amour >- Match Tests >- Typed Racket Tests >- Typed Racket Updates: update HISTORY >(updates should show v5.3.6 as the most current version; email me >to pick the changes when they're done, or tell me if there are no such >changes.) I get the following error when runing the TR tests: place-channel-put: value not allowed in a message value: '#:methods ... Is 733907474190da499a1782b230086170c5b87643 missing from the release? Now running the tests without places. Vincent _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Pre-Release Checklist for v5.3.6
On Mon, Jul 22, 2013 at 3:13 PM, Ryan Culpepper wrote: > * Carl Eastlund > - Dracula Tests (confirm that Dracula runs from PLaneT) > Done. _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] `#%declare' and cross-phase persistent modules
I'm seeing that in a fresh build. (Didn't see it before, because I had mangled my build.) I'll push a repair shortly. At Mon, 22 Jul 2013 17:14:49 -0400, Stephen Chang wrote: > When compiling a fresh git head clone, I still get some cross-phase > persistence errors (see below). Is this my fault, or are some packages > still missing the declaration? > > > raco setup: --- checking package dependencies --- > raco setup: > raco setup: error: during making for > /errortrace-doc/errortrace/scribblings > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /errortrace-lib/errortrace > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /errortrace-lib/errortrace > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /errortrace-lib/errortrace > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /errortrace-lib/errortrace > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /errortrace-lib/errortrace > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /errortrace-lib/errortrace/lang > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /algol60 > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/drscheme > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/drracket > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/drracket/private > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/scribble/tools > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/scribblings/tools > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/scribblings/tools > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/scribblings/tools > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/scribblings/drracket > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/drracket/private > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/scribblings/drracket > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/drracket/private > raco setup: module: does not satisfy cross-phase persistent grammar > > On Mon, Jul 22, 2013 at 12:18 PM, Matthew Flatt wrote: > > As of v5.90.0.2 (pending), to declare a cross-phase persistent module, > > the module body must include > > > > (#%declare #:cross-phase-persistent) > > > > If the module declaration fails to meet the syntactic and import > > constraints of a cross-phase persistent module, then a syntax error is > > reported. > > > > This change is backward-incompatible in two ways: > > > > * Module declarations that are intended as cross-phase persistent > >won't be, anymore, until a `#%declare' form is added. > > > >I think cross-phase persistence is new enough --- and the old, quiet > >inference of persistence is sufficiently distressing --- that this > >won't be much of an issue. > > > > * The grammar of fully-expanded modules now includes `#%declare' > >forms. > > > >Programs that process fully-expanded modules are not common, but I > >expect that they exist outside of the main distribution. Those > >programs will need to be updated. Meanwhile, they won't break until > >they see a module that has a `#%declare' form, which won't happen > >often (at least for the near future). > > > > Although `#:cross-phase-persistent' is the only keyword recognized by > > `#%declare' initially, we'll add more. One possibility is a declaration > > that corresponds to `compile-enforce-module-constants'. > > > > I named the form `#%declare' instead of `declare' to avoid conflicts, > > and also because I expect the form to be used more often in macro > > expansions than directly, so it seems like a "#%" kind of form. > > > > _ > > Racket Developers list: > > http://lists.racke
Re: [racket-dev] `#%declare' and cross-phase persistent modules
I get the same thing. Also, the error message is particularly unhelpful. It does not give the name of the module, a source location, or any indication of what part of the module did not match what part of the grammar in what way. This is pretty much impossible to debug without searching for every use of #%declare in the code base, and tracking down every macro that can possibly expand into it. Carl Eastlund On Mon, Jul 22, 2013 at 5:14 PM, Stephen Chang wrote: > When compiling a fresh git head clone, I still get some cross-phase > persistence errors (see below). Is this my fault, or are some packages > still missing the declaration? > > > raco setup: --- checking package dependencies --- > raco setup: > raco setup: error: during making for > /errortrace-doc/errortrace/scribblings > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /errortrace-lib/errortrace > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /errortrace-lib/errortrace > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /errortrace-lib/errortrace > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /errortrace-lib/errortrace > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /errortrace-lib/errortrace > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /errortrace-lib/errortrace/lang > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /algol60 > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/drscheme > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/drracket > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/drracket/private > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/scribble/tools > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/scribblings/tools > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/scribblings/tools > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/scribblings/tools > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/scribblings/drracket > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/drracket/private > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/scribblings/drracket > raco setup: module: does not satisfy cross-phase persistent grammar > raco setup: > raco setup: error: during making for /drracket/drracket/private > raco setup: module: does not satisfy cross-phase persistent grammar > > On Mon, Jul 22, 2013 at 12:18 PM, Matthew Flatt > wrote: > > As of v5.90.0.2 (pending), to declare a cross-phase persistent module, > > the module body must include > > > > (#%declare #:cross-phase-persistent) > > > > If the module declaration fails to meet the syntactic and import > > constraints of a cross-phase persistent module, then a syntax error is > > reported. > > > > This change is backward-incompatible in two ways: > > > > * Module declarations that are intended as cross-phase persistent > >won't be, anymore, until a `#%declare' form is added. > > > >I think cross-phase persistence is new enough --- and the old, quiet > >inference of persistence is sufficiently distressing --- that this > >won't be much of an issue. > > > > * The grammar of fully-expanded modules now includes `#%declare' > >forms. > > > >Programs that process fully-expanded modules are not common, but I > >expect that they exist outside of the main distribution. Those > >programs will need to be updated. Meanwhile, they won't break until > >they see a module that has a `#%declare' form, which won't happen > >often (at least for the near future). > > > > Although `#:cross-phase-persistent' is the only keyword recognized by > > `#%declare' initially, we'll add more. One possibility is a declaration > > that corresponds to `compile-enforce-module-constants'. > > > > I
Re: [racket-dev] `#%declare' and cross-phase persistent modules
When compiling a fresh git head clone, I still get some cross-phase persistence errors (see below). Is this my fault, or are some packages still missing the declaration? raco setup: --- checking package dependencies --- raco setup: raco setup: error: during making for /errortrace-doc/errortrace/scribblings raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /errortrace-lib/errortrace raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /errortrace-lib/errortrace raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /errortrace-lib/errortrace raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /errortrace-lib/errortrace raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /errortrace-lib/errortrace raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /errortrace-lib/errortrace/lang raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /algol60 raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /drracket/drscheme raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /drracket/drracket raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /drracket/drracket/private raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /drracket/scribble/tools raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /drracket/scribblings/tools raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /drracket/scribblings/tools raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /drracket/scribblings/tools raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /drracket/scribblings/drracket raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /drracket/drracket/private raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /drracket/scribblings/drracket raco setup: module: does not satisfy cross-phase persistent grammar raco setup: raco setup: error: during making for /drracket/drracket/private raco setup: module: does not satisfy cross-phase persistent grammar On Mon, Jul 22, 2013 at 12:18 PM, Matthew Flatt wrote: > As of v5.90.0.2 (pending), to declare a cross-phase persistent module, > the module body must include > > (#%declare #:cross-phase-persistent) > > If the module declaration fails to meet the syntactic and import > constraints of a cross-phase persistent module, then a syntax error is > reported. > > This change is backward-incompatible in two ways: > > * Module declarations that are intended as cross-phase persistent >won't be, anymore, until a `#%declare' form is added. > >I think cross-phase persistence is new enough --- and the old, quiet >inference of persistence is sufficiently distressing --- that this >won't be much of an issue. > > * The grammar of fully-expanded modules now includes `#%declare' >forms. > >Programs that process fully-expanded modules are not common, but I >expect that they exist outside of the main distribution. Those >programs will need to be updated. Meanwhile, they won't break until >they see a module that has a `#%declare' form, which won't happen >often (at least for the near future). > > Although `#:cross-phase-persistent' is the only keyword recognized by > `#%declare' initially, we'll add more. One possibility is a declaration > that corresponds to `compile-enforce-module-constants'. > > I named the form `#%declare' instead of `declare' to avoid conflicts, > and also because I expect the form to be used more often in macro > expansions than directly, so it seems like a "#%" kind of form. > > _ > Racket Developers list: > http://lists.racket-lang.org/dev _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Pre-Release Checklist for v5.3.6
At Mon, 22 Jul 2013 15:13:28 -0400, Ryan Culpepper wrote: > * 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 >- Try compiling with -funsigned-char >- Try compiling with TEST_ALTERNATE_TARGET_REGISTER Done. >Updates: >- Racket Updates: update HISTORY >(updates should show v5.3.6 as the most current version) >- Update man pages in racket/man/man1: racket.1, gracket.1, raco.1 No changes. _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] package-system update
At Mon, 22 Jul 2013 20:48:14 +0200, Togan Muftuoglu wrote: > However one thing is missing, the man pages are not installed by the make > install phase. For openSUSE (yet it should be the same for other distros) > every executable file should have a man page. I've updated "info.rkt" files so that the man pages we have are now installed. There are still many executables without man pages (i.e., we never had them). _ Racket Developers list: http://lists.racket-lang.org/dev
[racket-dev] Pre-Release Checklist for v5.3.6
Checklist items for the v5.3.6 release
(using the v5.3.5.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.racket-lang.org/release/installers
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 directory in such a directory, you can do this:
cd ...racket-root...
git archive --remote=git://git.racket-lang.org/plt.git release \
-- collects/tests | tar x
--
* 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
- Try compiling with -funsigned-char
- Try compiling with TEST_ALTERNATE_TARGET_REGISTER
Updates:
- Racket Updates: update HISTORY
(updates should show v5.3.6 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 v5.3.6 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 v5.3.6 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 v5.3.6 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
Updates:
- Teachpack Updates: update HISTORY
(updates should show v5.3.6 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 Classifier Tests
- RackUnit GUI Tests
- Data Tests
- DB Tests
* Jay McCarthy
- Web Server Tests
- XML Tests
- HTML Tests
- PLAI Tests
- Racklog tests
- Datalog tests
* Kathy Gray
- Test Engine Tests
* Noel Welsh
- Rackunit Tests
- SRFI Tests
- Ensure that all claimed srfi's are in the installer and they all
load into racket or drracket (as appropriate)
* 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")
Version Updates: if a major change has happened, update the version
number in:
- racket/collects/mzscheme/info.rkt
- racket/collects/mred/info.rkt
* Stephen Bloch
- Picturing Programs Tests
* Greg Cooper
- FrTime Tests
* Carl Eastlund
- Dracula Tests (confirm that Dracula runs from PLaneT)
* 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
* Danny Yoo
-
Re: [racket-dev] package-system update
> On Sun, 21 Jul 2013 10:32:10 -0600, Matthew Flatt > said: Matthew> When the "gui" (or "gui-lib") package is installed, then a Matthew> "gracket" executable is added to "bin". The "starter" executable Matthew> is used by `raco exe' to generate executables (that sometimes Matthew> refer back to "gracket"). Ok there is progress to report, I can now build the core package alone. However one thing is missing, the man pages are not installed by the make install phase. For openSUSE (yet it should be the same for other distros) every executable file should have a man page. Thanks Togan -- o.o.o o_o__o _o ,_o o_ <|> `|' (|))'),' ` |( ' (, ,( )| ' ( ) [ ] [ ]>\ / >< \/<< \/ > _ Racket Developers list: http://lists.racket-lang.org/dev
[racket-dev] `#%declare' and cross-phase persistent modules
As of v5.90.0.2 (pending), to declare a cross-phase persistent module, the module body must include (#%declare #:cross-phase-persistent) If the module declaration fails to meet the syntactic and import constraints of a cross-phase persistent module, then a syntax error is reported. This change is backward-incompatible in two ways: * Module declarations that are intended as cross-phase persistent won't be, anymore, until a `#%declare' form is added. I think cross-phase persistence is new enough --- and the old, quiet inference of persistence is sufficiently distressing --- that this won't be much of an issue. * The grammar of fully-expanded modules now includes `#%declare' forms. Programs that process fully-expanded modules are not common, but I expect that they exist outside of the main distribution. Those programs will need to be updated. Meanwhile, they won't break until they see a module that has a `#%declare' form, which won't happen often (at least for the near future). Although `#:cross-phase-persistent' is the only keyword recognized by `#%declare' initially, we'll add more. One possibility is a declaration that corresponds to `compile-enforce-module-constants'. I named the form `#%declare' instead of `declare' to avoid conflicts, and also because I expect the form to be used more often in macro expansions than directly, so it seems like a "#%" kind of form. _ Racket Developers list: http://lists.racket-lang.org/dev
