> Could you explain that? I do similar things (just that not everything > of it is published for $reasons), and I can't see how its increasing my > workload as git and CIs are doing these things for me. > > So I'm always curious on why workloads increase just by maintining a > package on salsa. It doesn't increase because of salsa. It increases because instead of being maintained on once place it goes in 2 places, where I still have to maintain both (by myself, mostly). I normally run "make deb-pkg" which creates a .orig.tar.gz, signs it, then puts the debian/ directory somewhere suitable and builds it with dpkg- buildpackage. If the debian/ directory is on salsa, but the rest of the project is somewhere else, then this no longer works, I have to tag in 2 different places, I have 2 different repositories to push to and so on. And what's the advantage? When an nmu happens the person doing it normally doesn't bother to push to salsa anyway. At most I get a patch in the bugreport, or I have to diff the packages and import the diff. So, extra complications for no actual advantage, from my experience. -- Salvo Tomaselli "Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno." -- Galileo Galilei https://ltworf.codeberg.page/
Attachment:
signature.asc
Description: This is a digitally signed message part.