I tried running raco setup, and got two kinds of errors (after which I got the same error as before when trying to run Scribble):
- "expected a 'module' declaration ..." arising from a bunch of my own files (some that are reachable from my link and some that are within my GitHub directories that are not connected to link commands) - a bunch of delete-file errors such as raco setup: launcher: <gui-bin>/DrRacket.exe delete-file: cannot delete file path: C:\Program Files (x86)\Racket\DrRacket.exe system error: Permission denied; errno=13 raco setup: launcher: <gui-bin>/PLT Games.exe delete-file: cannot delete file path: C:\Program Files (x86)\Racket\PLT Games.exe system error: Permission denied; errno=13 ... On Sat, Mar 15, 2014 at 11:52 AM, Matthew Flatt <[email protected]> wrote: > Yes, the intent is that you should be able to take your time to convert > from links to packages. > > Like Jay, I wonder whether you ran `raco setup` after `raco link` --- > in contrast to `raco pkg install`, which runs `raco setup` as needed > for you. A linked collection's libraries can be found for running > without a `raco setup`, while documentation cross-referencing would > depend on `raco setup`. > > (Jay: I think it's no longer the case that `raco setup` as run by > `make` in a repo checkout ignores your links. If I understand what you > have in mind and if I remember correctly, that's a change relative to > v5.3.6.) > > At Fri, 14 Mar 2014 16:05:56 -0600, Jay McCarthy wrote: > > Is it possible that the old link is version specific? Have you run a > > full "raco setup" after upgrading? (The default "raco setup" that runs > > during the build process will only look at the core and ignore your > > links.) > > > > On Fri, Mar 14, 2014 at 7:59 AM, Kathi Fisler <[email protected]> > wrote: > > > I have a custom #lang (a scribble extension). In previous versions, I > used > > > raco link to register the directory containing the lang.rkt and other > files > > > for my #lang. > > > > > > After switching to 6.0, scribble yields an error that suggests it is > not > > > finding the functions defined in my #lang. I have rerun the raco link > > > command, and confirmed that the link is there (through raco link -l). > I get > > > no errors when I attempt to "run" the lang.rkt file or the file > containing > > > the unfound functions. > > > > > > Might this be an artifact of the new package system, or am I looking > > > elsewhere for the problem? I couldn't tell whether I had to switch > over to > > > the new package system now, or whether I can take my time migrating our > > > stuff over. > > > > > > thanks, > > > Kathi > > > > > > > > > > > > > > > ____________________ > > > Racket Users list: > > > http://lists.racket-lang.org/users > > > > > > > > > > > -- > > Jay McCarthy <[email protected]> > > Assistant Professor / Brigham Young University > > http://faculty.cs.byu.edu/~jay > > > > "The glory of God is Intelligence" - D&C 93 > > ____________________ > > Racket Users list: > > http://lists.racket-lang.org/users > >
____________________ Racket Users list: http://lists.racket-lang.org/users
