psa please don't use git submodules for packages that are in every OS's repos tyvm
bonifartius 𒂼𒄄
@velartrill "please don't use git submodules" ;)
@bonifartius @velartrill they are nice for keeping track of which version of dependencies something does a clean build with.
if you use something like meson you can actually set it not to use the vendored dependency if one already exists on the system which is comf
if you use something like meson you can actually set it not to use the vendored dependency if one already exists on the system which is comf
@icedquinn i know it is almost universally hated, but i think vendoring if done right is much better than everything else. maybe throw in a switch to select using vendored or system libs for building.
when packaging submodules are a pain, when developing it isn't much better imho.
it's just my taste though :)
@bonifartius @velartrill for local informal stuff I don’t version at all. but otherwise I like to vendor external stuff just to guarantee a buildable state.
a sad amount of Go code is basically ewaste because nothing is versioned and you’ll never find the combination of git hashes it all required to compile that old version
a sad amount of Go code is basically ewaste because nothing is versioned and you’ll never find the combination of git hashes it all required to compile that old version
Follow
@icedquinn i think it depends on the school of go code. you have the "go guarantee"-never-break-things kind of code where you almost never need any versioning.
then you have the "mOvEfAsTaNdBrEaKtHinGs!!1" kind of code which is just a shit show. usually libraries which do too much and use go in a way it never was supposed to be used (like abusing reflection for everything, etc.).
