situation looks like this:

§lambda1:/home/deep> ls
...  liquid  liquid-doc  liquid-lib  ...

§lambda1:/home/deep> cat liquid-doc/info.rkt 
#lang info

(define collection 'multi)
(define deps '("base"))
(define build-deps '("scheme-lib"
                     "racket-doc"
                     "syntax-color-doc"
                     "liquid-lib"
                     "scribble-lib"))

(define pkg-desc "documentation part of \"liquid\"")

(define pkg-authors '(twlynch))

§lambda1:/home/deep> cat liquid-doc/liquid/info.rkt 
#lang info

(define scribblings '(("liquid.scrbl" (multi-page) 
(deep-web-search-framework))))

And in my home directory:

§lambda1:/home/deep> ls -1 ~/.racket/6.1/doc/
blueboxes.rktd
docindex.sqlite
doc-site.css
doc-site.js
index.html
in.sxref
local-redirect
manual-fonts.css
manual-racket.css
manual-racket.js
manual-style.css
out0.sxref
out1.sxref
provides.sxref
racket.css
release
scribble-common.js
scribble.css
scribble-style.css
search
stamp.sxref
synced.rktd

I did run scribble -htmls inside of liquid-doc/liquid/doc  and created the 
documentation so I can now work on formatting and editing it.  

no index.html in ~/.racket/6.1/doc or subdirs for the liquid package.  Have 
I messed up the info.rkt files?  

When this is done right, will there be a way to navigate from the 
~/racket/6.1/doc/index.html and get to the package doc pages?  Or will one 
always pull out the package docs from a 
file:///~/.racket/doc/liquid/index.html  url?

One other source of confusion, the scribble docs described the option of 
putting the scribble in with the source code.  However the 
/usr/share/racket/pkgs were not done this way.  Is this a preferred 
approach, or just a separate feature from the way the usual libs are done?  
Seems it would be difficult to write docs that way, but sure would make it 
easier to keep usage examples in sync.

-- 
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/b9d6cca3-2a73-4eca-84ee-d108698fda23%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to