Open colisee opened 1 year ago
Hi @colisee,
thank you for the suggestion!
Originally I wanted to keep the documentation short here and mainly refer to the documentations of dpkg-buildpackage
and the other involved tools. But I see that it would be helpful to show more than just the most trivial use case in the action’s readme, as it’s currently done.
Will think about how to present your use case (thanks for the code) and maybe others. Will keep this issue open for now as a reminder to myself.
In case you find any problems with other use cases, please let me know!
Hi @jtdor,
This is the least I could do!
For your information, you can find the full github action (which uses a matrix strategy) here
Please note that I modified the before-build-hook
argument in my action because I had several tars listed by the command pristine tar checkout
. As a reminder, the pristine command works if your git repository contains a pristine-tar
branch (in my case generated through git-buildpackage)
Cheers.
Hi,
the documentation does not mention how to generate source and binary (which is the default behavior for dpkg-buildpackage)
This is the github action code I used in that respect:
Note:
pristine-tar
branch that contains the upstream tarball deltafetch-depth: 0
extra-build-deps: pristine-tar git
buildpackage-opts: --build=full
Feel free to add the above to your documentation, if you feel it could be of use.
Cheers.