3 ms·
Grabbing git repos instead of just tarballs is useful. A) You can update them, because you can git pull to fetch changes. B) If you want to apply patches on t
by kingstnap 6mo ago
Grabbing git repos instead of just tarballs is useful.
A) You can update them, because you can git pull to fetch changes.
B) If you want to apply patches on top, its better to have version control so you can keep track of what you changed, especially useful if you want to rebase.
- skydhash 6mo agoA) only valid if you want to stay with the devel version B) See A I use OpenBSD and before that, I was on alpine, debian, and arch. Of it was a software I want to try, I downloaded the tarball. if it’s something I wanted to keep for longer, I created a port or a custom packages.
- xyzzy_plugh 6mo agoOf course it's valid for release versions too: just fetch and checkout the release tag you want. I do this all the time. Juggling multiple directories and tarballs is a pastime from a bygone era. It's even more commands if you want to reuse the existing directory!
- kingstnap 6mo agoYou should invert your framing. It's only *not valid* if you intend to use a fixed version forever. Otherwise you might as well include versioning for any other case.
- skydhash 6mo ago> Otherwise you might as well include versioning for any other case. It’s easier to version a port and the patches than to try keeping a series and patches on top of a dev branch. Not saying that your use cases are invalid, but the point of the thread was using git for building software. If you’re not developing the software, there’s no need to go from something that is working well to an unstable build every week.