Actually, the libraries can't be reached either.  Tried installing from 
both the level above and the dir with the sources:

§lambda1:/home/deep/liquid-lib/liquid> raco pkg install
raco pkg install: package is already installed from a different source
  package: liquid
  installed source: (link ../../../../deep/liquid)
  given source: (link ../../../../deep/liquid-lib/liquid)


But in the REPL, using one of the modules defined in liquid-lib/liquid

Welcome to Racket v6.1.

racket@> (require realtime.rkt)
stdin::356: realtime.rkt: bad module path
  in: realtime.rkt
  context...:
   standard-module-name-resolver
   /usr/share/racket/collects/racket/private/misc.rkt:87:7


Realtime.rkt is defined in the new lib.  Anyway, and FYI to tie off the 
last open thread here.
 


On Monday, April 20, 2015 at 8:34:26 PM UTC+8, robby wrote:
>
> Also, the command "raco docs" with no arguments takes you to the 
> starting point for the documentation. This starting point can move 
> based on what packages you have installed, I believe (it can move from 
> a file that comes with a distribution into a user-specific place when 
> you have installed user-specific pkgs), so if you want to check what 
> Racket thinks the current starting point is, that's a good way to do 
> it. 
>
> Robby 
>
>
>
> On Mon, Apr 20, 2015 at 6:22 AM, Alexander D. Knauth 
> <alex...@knauth.org <javascript:>> wrote: 
> > If you want to see it in the docs, I think you have to do one of these 
> > things: 
> >  - raco pkg install —link path-to/liquid-lib path-to-liquid-doc 
> > path-to/liquid 
> > or 
> >  - raco pkg install ; in the directory of first liquid-lib, then 
> liquid-doc, 
> > then liquid 
> > or 
> >  - do what you just did, but for each of the three packages, and then 
> run 
> > raco setup liquid 
> > 
> > 
> > On Apr 20, 2015, at 4:22 AM, Thomas Lynch 
> > <thomas...@reasoningtechnology.com <javascript:>> wrote: 
> > 
> > So apparently my new 'liquid' package is installed locally: 
> > 
> > §lambda1:/usr/share/doc/racket> raco link -l | grep liquid 
> >  root  path: "/home/deep/liquid-lib" 
> >  root  path: "/home/deep/liquid-doc" 
> >  root  path: "/home/deep/liquid" 
> > 
> > §lambda1:/usr/share/doc/racket> raco pkg show 
> > Installation-wide: 
> >  Package              Checksum                                    Source 
> >  main-distribution    f07e2d4bf2708c1085be38eca18aa9eb6755e547   
>  (catalog 
> > main-distribution) 
> >  racket-lib           41c7b3221006758c5a840a18dcc0d265632f14c2   
>  (catalog 
> > racket-lib) 
> >  [175 auto-installed packages not shown] 
> > User-specific for installation "6.1": 
> >  Package    Checksum    Source 
> >  liquid     #f          (link ../../../../deep/liquid) 
> >  [2 auto-installed packages not shown] 
> > 
> > So then I open /usr/share/doc/racket/index.html in a browser and naively 
> > expect to find a link to the local "catalog" which would have a links to 
> the 
> > docs for my new package.  Ah but alas no.  Even grep -r  finds no 
> reference 
> > to my new package in my /home/twl/.racket directory,  in /usr/share/doc 
> or 
> > even in the /home/deep directory that holds the package data.  Come to 
> think 
> > of it,  raco install was run with just user privileged though it didn't 
> > complain.  Is that right?  Ok so let me try with supervisor privilege: 
> > 
> > §lambda1:/home/deep/liquid#  raco pkg install 
> > raco pkg install: missing dependencies; 
> >  specify `--deps search-auto' to install them, or 
> >  specify `--deps search-ask' to be asked about installing them 
> >   for package: /home/deep/liquid/ 
> >   missing packages: 
> >    liquid-lib 
> >    liquid-doc 
> > 
> > Oh gosh, we are back to that again!  Running it as user: 
> > 
> > §lambda1:/home/deep/liquid> raco pkg install 
> > raco pkg install: package is already installed 
> >   package: liquid 
> > 
> > Ok, ah .. so where are the docs? 
> > 
> > 
> > -- 
> > 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 racket-dev+...@googlegroups.com <javascript:>. 
> > To post to this group, send email to racke...@googlegroups.com 
> <javascript:>. 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/racket-dev/b8775fa1-b77c-411f-bfcf-0cbb50ee0631%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 racket-dev+...@googlegroups.com <javascript:>. 
> > To post to this group, send email to racke...@googlegroups.com 
> <javascript:>. 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/racket-dev/5C9EE29E-5B46-474F-87BA-410C1DFA159A%40knauth.org.
>  
>
> > 
> > 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 racket-dev+unsubscr...@googlegroups.com.
To post to this group, send email to racket-dev@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-dev/14bc1d25-63a5-4f45-b407-45391dce7dc5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to