Closed intelfx closed 11 months ago
Well, this is sort of unfortunate. The difference between 'update' and 'checkout' is such that I only commit to keeping around a copy of the blobs when the user requests the checkout. Everything else asp does is lighter weight and only needs the branches and histories. Whereas the current asp cache is only a few kilobytes, such a change could potentially make the cache hundreds of megabytes.
Thoughts? I'd really like to stay away from the idea of some sort of repository of local checkouts, as well.
I apologize for not getting back in over a year, but...
I'm not sure what the problem is. Asp already fetches all the blobs on asp update
, it simply does not create a local branch out of that history (only a remote one).
https://github.com/intelfx/asp/commit/36ba405952ca1316211622663c88be2a99efb527 fixes the issue for me. Does this make any more sense?
If
$ASPROOT
(~/.cache/asp
) has been purged for some reason,asp update PACKAGE
does not recreate the local branch for the pkgbase. This creates a problem because any existing asp checkouts become broken until another (pointless) checkout has been made:After purging the cache: