Hello, I must be doing this wrong. I created a package (now at github.com/Antigonus/liquid.git). It is broken into liquid, liquid-lib, and liquid-doc like other packages I see in the contributions.
There are many local function tests hooked into a list. These were used mostly before the installing the package, and are stable. That is nice. I am writing some examples using the locally installed package. Invariably I'm running into features and change issues for the package, and bugs. So here is the problem. To make a change, this is what I am doing: 1. raco pkg remove liquid -- I have to do this because otherwise there are dependency problems. 2. raco pkg remove liquid-lib 3. make changes (takes very little time) 4. cd to liquid-lib and raco pkg install ... etc. 5. test, find things, or introduce the next change item on the list, and repeat Going through this loop takes a gawdawful long time. About 1/8 cup of sipped coffee or two facebook posts (these are official developer time units ;-). Ten little changes and runs through this loop can be an hour. (If I run into those cases of errors without line numbers then a change can take an afternoon). I can reduce the time a little bit by removing the liquid dependency. But still the remove and replace of liquid-lib takes a long time. At one point I added a symbolic link from the example directory to the liquid-lib directory, and named the link 'liquid' .. but this doesn't actually work because the naming convention for installed modules is different than that for locally required modules, hence I also had to add '.rkt' and put quotes around the module names. This helps when changes are isolated and one spends time in a one or two files so that munging of names is an incremental cost ... Surely there is a better way to bring up examples and a library together??? I would very much appreciate learning how to do this correctly! Thanks! -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/44a58e04-45be-43be-8215-9427eed8f4ec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
