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
Similarly to jj, which takes a snapshot of the filesystem on every invocation of the program, rocks could create read-only files derived from the configuration upon every invocation (maybe even a rocks regenerate or whatever).
I guess the question is: do we want to make rocksthis automatic, or should we leave those files up to the user? I don't think this is trying to reinvent nix, but instead making sure that many developers are on the same page at all times.
The text was updated successfully, but these errors were encountered:
I was wondering whether it could be beneficial to contain all metadata inside the
project.rockspec
file, like so:Similarly to
jj
, which takes a snapshot of the filesystem on every invocation of the program,rocks
could create read-only files derived from the configuration upon every invocation (maybe even arocks regenerate
or whatever).I guess the question is: do we want to make
rocks
this automatic, or should we leave those files up to the user? I don't think this is trying to reinvent nix, but instead making sure that many developers are on the same page at all times.The text was updated successfully, but these errors were encountered: