I tried it. It works, but DrRacket doesn't find the macro stepper tool.
The racket/lib/info-cache.rktd has an entry for the right location, but
it also has another (lib "macro-debugger") entry. Is this caused by
having multiple modules "named" macro-debugger/info?
BTW, something is still populating
racket/lib/collects/info-domain/compiled/cache.rktd (rather than
racket/lib/info-cache.rktd). I thought the info-domain collection would
have disappeared. (And I thought it would be in racket/etc, but that
seems not to be the case.)
I tried rebasing one of my branches to the 'pkg' branch yesterday, and
that seems to have worked. With Carl's advice, the next time might go
even easier.
Is there a reason for the pkgs/*-pkgs groupings? I think I'd prefer pkgs
to contain just packages, but maybe I'm overlooking a benefit.
Ryan
On 06/18/2013 12:47 PM, Matthew Flatt wrote:
Here's the latest (in a "pkg2" branch):
https://github.com/mflatt/racket/tree/pkg2
Because this change will break all sorts of things in the short run,
I'd like to feel more confident that enough of us are ready before
merging it to the main Racket repository.
So, vote in favor of the reorganization like this:
1. Try the branch:
git clone https://github.com/mflatt/racket.git
cd racket
git checkout pkg2
make
racket/bin/drracket
2. Reply to the list to say that it works and we should merge it.
3. If you have code in "pkgs", be ready to help get that code into the
right shape/packages after the merge.
Thanks!
(We haven't yet changed anything about single-collection versus
multi-collection packages. That's currently planned for right after the
merge.)
_________________________
Racket Developers list:
http://lists.racket-lang.org/dev
_________________________
Racket Developers list:
http://lists.racket-lang.org/dev
