Alright, of course, raco pkg update is looking for new versions to install, it is not a make like utility just touching only modified parts. Is there a make like option for install that only updates modified parts?
On Fri, Jul 17, 2015 at 8:09 PM, Thomas Lynch < [email protected]> wrote: > oh excuse me Matt, why I "uninstall" > > If I don't uninstall I get this: > > 1. edit some module in the collection > 2. then type: > > > raco pkg install > raco pkg install: package is already installed > package: liquid-lib > > > 3. oops so try: > > > raco pkg update liquid-lib > raco pkg update: cannot update linked packages without `--link' > package name: liquid-lib > package source: /home/deep/liquid-lib > > ok earlier I was getting a more serious error with update that I thought > implied I couldn't use it, perhaps something with the code at that point, > that doesn't happen every time, so update is probably the answer. What is > the deal with link? If this is the default, what am I typing here? > > > raco pkg update --help > / --link : Link a directory package source in place (default for a > directory) > | --static-link : Link in place, promising collections do not change > > > > On Fri, Jul 17, 2015 at 7:57 PM, Thomas Lynch < > [email protected]> wrote: > >> >> >> On Fri, Jul 17, 2015 at 5:19 PM, Matthew Flatt <[email protected]> >> wrote: >> >>> Can you say more about why you uninstall "liquid-lib"? >>> >> >> I installed the package so I could use it. >> >> I am going through the pain of working with an unstable library so others >> won't have to so much. Plus, I am writing an application of my own using >> the library. There is nothing like putting something to use to find out >> what you really need from it. >> >> So in examples/early applications I have, (require liquid/red-lib) >> instead of (require "path/red-lib.rkt"), just like a user would have. >> >> >>> If you're uninstalling so you can use `raco pkg install` to rebuild the >>> package's contents, then you can use `raco setup liquid` instead of >>> uninstalling and re-installing. >>> >> >> Yeah, I figured that out for the documents. It works out well for them >> because they aren't called out in from any nascent application modules. >> >> .. I wish I could set a search path or something during this early use >> phase so as to be able to modify the library without having the uninstall >> and compile reinstall steps on every trip through the >> modification-compile-test cycle.. You know, just like it was lisp code or >> something ;-) If I could remove those steps things would go more smoothly >> at this stage. >> >> >> >> >> >>> At Fri, 17 Jul 2015 01:50:13 -0700 (PDT), Thomas Lynch wrote: >>> > 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-9427eed8f4 >>> > ec%40googlegroups.com. >>> > For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- 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/CAGxFmCNWihCTFskKTRHn3uYhs17rCsqjKi0ei%3DoBA9J_%3Dfhg2A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
