As described here <>,

> When a Git repository is specified as a package source, then a copy of the
> repository content is installed as the package implementation. That
> installation mode is designed for package consumers, who normally use a
> package without modifying it.

My understanding is that "the copy of the repository content" is produced
simply, e.g., by checking out the repository at the appropriate commit and then
discarding the `.git` directory.

An alternative would be to produce the repository content by running `git
archive`.  This would allow certain transformations to be made on the content,
e.g., inserting the commit hash into one of the exported files.  One could do
other minor tricks as well, like excluding "junk" files.  See the ATTRIBUTES
section of the man page at <>.

Is there a reason why the Racket package system doesn't run `git archive` to
produce the content for the "non-developer" version of a package?

Thanks ---


Eric Eide <>  .         University of Utah School of Computing . +1 (801) 585-5512 voice, +1 (801) 581-5843 FAX

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 view this discussion on the web visit
For more options, visit

Reply via email to