I was looking at the manual online:
And I found a mention of "repository packs" in the "darcs get"
documentation. I thought it sounded interesting, so searched further for
information about "repository packs", but there are no other hits. The
manual lacks a definition for what this term means, as well as how to
evaluate when to choose "--packs" vs "--no-packs" when using "darcs
I look forward towards taking advantage of this great feature.
Below is some proposed enhanced documentation for "darcs get" and "darcs
optimize" to improve the situation, based on what I've figured out so
far. However, I still have further questions which excellent
documentation should address:
* What happens if you run "darcs optimize --http" and then don't do it
for a month? How would performance and correctness change over time?
* Assuming you want to provide the best performance consistently over
HTTP, is there a best practice to make sure that the repository always
* What kind of additional disk space usage are packs expected to use,
proportional the repo size?
* In what cases would a user want to use --no-packs instead of --packs?
In the documentation for "optimize --http", it should say:
Using this option creates "repository packs" that could dramatically
speed up performance when a user does a "darcs get" of the repository
over HTTP. To make use of packs, the clients must have a darcs of at
least version 2.x.x. For more details, see
Then, in the "darcs get" documentation, it should say:
By default, darcs will look for and attempt to use packs created by
"darcs optimize --http"
The following patch sent by Guillaume Hoffmann <email@example.com> updated issue issue2102 with
* resolve issue2102: document packs in help of clone and optimize http
help string suggestions by Mark Stosberg