> On Nov 2, 2017, at 9:35 AM, Geoffrey Knauth <ge...@knauth.org> wrote: > > Let's suppose I want to have a preferences file, e.g., "~/.dbaccess.rkt". I > used to have a module I would import via > "../some-relative-path/dbaccess.rkt", but I thought I would try > "~/.dbaccess.rkt" as a module path. It turned out a module path cannot begin > with "/", which happens with the expansion of "~" (it seems). > > This leads me to the more general question, what do other people do, what is > the convention when, say, they will have a GitHub repo with generally public > code, but some private files with, say, database-access codes that are > specific to a person's use of a package?
One solution is to use a .gitignore. I have a convention that files ending with ‘private.rkt’ don’t go in the repo. Alternatively, you could have a single directory—a private repo, or not a repo at all—that’s linked as a package, containing a collection called ‘private’ or whatever you like, and then require them by using paths like (require private/dbaccess) Apologies if these were all too obvious for you! :) John -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.