Hi,
On Wed, Apr 10, 2024 at 09:09:13PM +0000, aquilamac...@riseup.net wrote:
> The ${RELEASE} variable in the context of this issue refers to the
> specific Debian release being used during the Salsa CI process. One
> potential solution that has been considered is to ensure that
> blhc:${RELEASE} correctly handles the flags for each release. This
> approach could alleviate the compilation errors and ensure consistency
> across different Debian releases.
>
> For more details, you can check the issue in the Salsa CI repository at
> https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/340
>
> Before proceeding with any changes, I would appreciate your input on
> this matter. Specifically, do you think it would be sensible to use blhc
> from each release? Your insights would be greatly appreciated.
I think the best solution is to use the blhc version from the
corresponding release (i.e. blhc:${RELEASE}). Otherwise each
change to flags in blhc will require manual work for earlier
releases as carnil mentioned.
The blhc version in each release should be able to handle the
flags for that release (otherwise it's a bug which should be
fixed). So the suggested first approach should work fine and
cause the less additional maintenance overhead.
Best,
Simon
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
signature.asc
Description: PGP signature
