Currently (AFAICT, please correct me if I'm wrong) there are multiple implementations of the "convert git repository source tree to Debian source package artifact" task. This results in different behaviour between users using docker-pkg-build and what happens in production.
|
def build_package_in_docker(image_name: str, source_dir: str, output_dir: str, distro: str, run_lintian: bool, extra_repo: str, extra_package: str, skip_gbp: bool, host_tmp_dir: str = None) -> bool: |
I'd like us all to converge on a single implementation please. I believe that https://github.com/qualcomm-linux/debusine-action/blob/main/lib/generate-source-package is the most current and best practice approach, but we can discuss if it doesn't do something that you need first.
Currently (AFAICT, please correct me if I'm wrong) there are multiple implementations of the "convert git repository source tree to Debian source package artifact" task. This results in different behaviour between users using docker-pkg-build and what happens in production.
docker-pkg-build/docker_deb_build.py
Line 375 in a054512
I'd like us all to converge on a single implementation please. I believe that https://github.com/qualcomm-linux/debusine-action/blob/main/lib/generate-source-package is the most current and best practice approach, but we can discuss if it doesn't do something that you need first.