Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

would (define collection 'multi) solve problem about compiled/ when racket version changes? #1

Open
AlexKnauth opened this issue Jan 26, 2015 · 2 comments

Comments

@AlexKnauth
Copy link

Every time I update my racket installation to a new version, this package gives me errors about compiled/ files and version mismatches, and it seems to be treating the info.rkt as a normal compiled file. Is it supposed to do that, and I'm wondering, would adding (define collection 'multi) possibly solve this? For multi-collect packages it doesn't seem to have a compiled/ dir for the info.rkt, and it seems like if those don't need it this shouldn't? Or should the framework:color-schemes be in a collection info.rkt not the package info.rkt?
(I know I should just run raco setup, but I'm also wondering how this works)

@takikawa
Copy link
Owner

That sounds like it could be a package system issue, since it seems odd that a single collection package wouldn't work properly for this use case. I'll see if I can reproduce it.

@AlexKnauth
Copy link
Author

It's not that it doesn't work properly, it's that it's annoying to have to recompile it when it seems like a package info.rkt for a multi-collect pkg doesn' need a compiled/ dir, but for a single-collect pkg it does, and since an info.rkt is basically all that is in this pkg, I'm wondering if the problem would go away for this pkg (I would still have to run raco setup for the other user pkgs though).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants