You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 26, 2024. It is now read-only.
I thought I had written this somewhere but I couldn't find it so here goes.
In development machines, I would like to preserve the same program being used in multiple projects by not having duplicates. Currently, two projects depending on the same program of the same version and same checksum would be downloaded twice and unaware of each other. I think we should merge them.
Roughly, provided ~/.bindl/ exists, it should have:
programs/ where all the programs are
locks/ symlinks to where all locks exists in the given host
This means that the behavior of bindl {get,purge,verify} would have to take into account these path changes.
I think the default should still do what we're doing currently, until at some point user runs bindl generate hostconfig or something similar, which creates ~/.bindl/, then the behavior starts changing. But thoughts on this are welcome!
The text was updated successfully, but these errors were encountered:
I learned about os.UserCacheDir and hacked up the caches of HTTP responses. I'm not exactly proud on this initial implementation (#53), but I think this solves half (reducing network calls) of this issue while the primary one (reducing disk usage) still yet to be solved.
I thought I had written this somewhere but I couldn't find it so here goes.
In development machines, I would like to preserve the same program being used in multiple projects by not having duplicates. Currently, two projects depending on the same program of the same version and same checksum would be downloaded twice and unaware of each other. I think we should merge them.
Roughly, provided
~/.bindl/
exists, it should have:programs/
where all the programs arelocks/
symlinks to where all locks exists in the given hostThis means that the behavior of
bindl {get,purge,verify}
would have to take into account these path changes.I think the default should still do what we're doing currently, until at some point user runs
bindl generate hostconfig
or something similar, which creates~/.bindl/
, then the behavior starts changing. But thoughts on this are welcome!The text was updated successfully, but these errors were encountered: