Arch Linux and Debian packaging

[Luis-HCarvalho]

Hi @koraa,

I've created a PKGBUILD file for Arch linux packages (currently in PR #7).

For Debian packaging, I've added the files debian/{changelog,control,copyright,rules} at "debian/latest" branch in my fork https://github.com/Luis-HCarvalho/pipe_exec/tree/debian/latest.

The content of "debian/latest" isn't intended for merging directly into "master". Therefore, if you judge this packaging useful for upstream, it might be better to create a dedicated branch (e.g, "debian/latest", "debian/<version>") for it.

P.S.: If you plan to use those Debian packaging files (e.g. debian/control) to submit a package you may need to edit the maintainer information.

[koraa]

@Luis-HCarvalho Thank you for your effort. It is most appreciated!

Can you explain to me, why is it better to keep the files on a dedicated branch?

I do not plan to operate as a debian maintainer, if you would be willing to maintain a package for debian, your contribution would be very welcome.

[Luis-HCarvalho]

Hi @koraa,

The dedicated branch for debian packaging files follows the layout proposed in DEP-14 ("Recommended layout for Git packaging repositories") at https://salsa.debian.org/dep-team/deps/-/blob/master/web/deps/dep14.mdwn.

The packaging related files I provided both for Arch and Debian, are intended to be more as practical packaging resources. This is, a convenient template for the actual packaging repositories or, as an alternative way to installation, for those that know how to use it to install the package with their respective package manager (i.e., pacman or apt).

I like the repository layout proposed by the DEP-14 conventions, but as this isn't a packaging repo, you may prefer to adopt another way to structure this repository.

[koraa]

@Luis-HCarvalho All right. Since this is a low-effort maintenance repo, I am merging your branch into our main branch. This way we won't have a divergence over time. Thanks for your contribution!