Re:What’s wrong with Git? A conceptual design analysis (2016)
by geofft on Tuesday April 27, 2021 @06:52PM
(#26962993)
Sure, then you have option 3: Put a "setup-git.sh" script in your repo, and have the README tell users to run that to set things up. If your users are willing to run code from your repo, you can just have them run code from your repo.
In fact you can set the default branch to contain nothing but those two files, and have the setup script switch to the real branch once it's done with its work.
(And if your users have some other way they expect to run code - make, setup.py, yarn run, whatever - you can use that instead as the entry point.)
Re:What’s wrong with Git? A conceptual design analysis (2016)
by rualca on Wednesday April 28, 2021 @01:40AM
(#26966017)
> Sure, then you have option 3: Put a "setup-git.sh" script in your repo, and have the README tell users to run that to set things up.
This is pretty good advice. If projects expect onboarders to run one-time scripts to install third-party dependencies, the least they can do is to also provide scripts to setup the development environment.
I understand the sentiment but I feel like this is just not true. Its designed to share code you plan to build and run, after all. As you say, it seems like we could solve it with signatures and trust but I doubt we'll ever get there, sadly.