Closed brokenpip3 closed 1 year ago
For the record, bats-support
is now in Debian testing and will be part of the next of Debian 12 (codename "bookwork"): https://tracker.debian.org/pkg/bats-support.
@gioele Seeing that there already is at least one package maintainer from Debian' side, do you feel that we should provide the package recipe in this repo at all?
For the record,
bats-support
is now in Debian testing and will be part of the next of Debian 12 (codename "bookwork"): https://tracker.debian.org/pkg/bats-support.
This is so nice, the problem is that the other packages (assert, file, detik) are not in the debian repos. How I can help with those? I can create and maintain those packages if needed.
@gioele Seeing that there already is at least one package maintainer from Debian' side, do you feel that we should provide the package recipe in this repo at all?
If you think that having those debian packages in the bats* repos will help let us know, I can create the PR based on your needs, thanks!
For the record,
bats-support
is now in Debian testing and will be part of the next of Debian 12 (codename "bookwork"): https://tracker.debian.org/pkg/bats-support.This is so nice, the problem is that the other packages (assert, file, detik) are not in the debian repos.
bats-assert
is ready, waiting in the sponsoring pipeline and will be officially available in a matter of days. bats-file
is also ready to go. (bats-file
seems much less curated than the others, but that's a discussion for another day.)
With the initial packaging done, the maintenance burden is now quite low.
How I can help with those? I can create and maintain those packages if needed.
Help with bats-detik
would be nice, as none of use co-maintainers use it. Send me an email (see the package details).
@gioele Seeing that there already is at least one package maintainer from Debian' side, do you feel that we should provide the package recipe in this repo at all?
Debian (both the technical packaging infrastructure and the project as a whole) is generally against upstream project shipping recipes to build Debian packages. The main reason being that such recipes are rarely able to keep up with the evolution of the ecosystem and they do not benefit from the CI and QA infrastructure of Debian (autopkgtests, piuparts, debci, tracker.d.o, …). In addition these are relative simple packages, so it is often possible to download the .deb
files from packages.debian.org and install them in Debian-derived distros without any issue.
@gioele Seeing that there already is at least one package maintainer from Debian' side, do you feel that we should provide the package recipe in this repo at all?
Debian (both the technical packaging infrastructure and the project as a whole) is generally against upstream project shipping recipes to build Debian packages. The main reason being that such recipes are rarely able to keep up with the evolution of the ecosystem and they do not benefit from the CI and QA infrastructure of Debian (autopkgtests, piuparts, debci, tracker.d.o, …). In addition these are relative simple packages, so it is often possible to download the
.deb
files from packages.debian.org and install them in Debian-derived distros without any issue.
I understand this as: no we (bats-core org) don't need to provide Debian recipes, correct? If so, I will close this PR.
I understand this as: no we (bats-core org) don't need to provide Debian recipes, correct? If so, I will close this PR.
Correct. The next version of Debian (and derivatives) will contain up-to-date packages for bats
, bats-support
and bats-assert
.
If you are interested I can create the same PR with bats file, detik and assert (and rpm version as well)