canonical / flamenco

Maintenance tools for packaging toolchains on Ubuntu

Flamenco

Maintenance tools for packaging toolchains on Ubuntu.

License

Flamenco Copyright (C) 2024 Canonical Ltd.

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License version 3 as published by the Free Software Foundation.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see https://www.gnu.org/licenses/.

flamenco's Issues

Add support for referenced Git repositories

This idea came up when thinking about the debian/eng/test-runner and debian/tests/regular-tests directories and how they essentially duplicate files already available and maintained in separate Git repositories.

So, in order to avoid also having these files in the debian/ source tree, we can make it so Flamenco understands external references to Git repositories in a structured and standardized file.

For example, inside the debian/eng/test-runner directory, we can have a file called flamenco-git.{source_package}.{release} (exact name TBD) that essentially states that that directory should contain the files present in x repository, at y commit or z tag, when building the dist folder of source_package targeting release.

The structure of that file can be something similar to:

repo=https://github.com/canonical/dotnet-test-runner
tag=v1.1.0
commit=eafbc12

Where tag xor commit are present. Exact structure also TBD.

In general, this solves for test-runner and regular-tests, but also allows us to make other components of the packaging external references, such as versionlib, and better separates the concerns of the source-build repo from the maintenance of these other libraries and tools.

As these are very preliminary thoughts, I'm open to discuss if and how we should make this even more general purpose.