Re: CI/yaml: inlining or providing an "upstream" utility

2024-03-27 Thread tlaronde
On Wed, Mar 27, 2024 at 09:00:12PM +1000, Peter Hutterer wrote: > On Mon, Mar 25, 2024 at 11:19:49AM +0100, tlaro...@kergis.com wrote: > > On Mon, Mar 25, 2024 at 08:07:24PM +1000, Peter Hutterer wrote: > > > On Mon, Mar 25, 2024 at 08:36:44AM +0100, tlaro...@kergis.com wrote: > > > > In a

Re: CI/yaml: inlining or providing an "upstream" utility

2024-03-27 Thread Peter Hutterer
On Mon, Mar 25, 2024 at 11:19:49AM +0100, tlaro...@kergis.com wrote: > On Mon, Mar 25, 2024 at 08:07:24PM +1000, Peter Hutterer wrote: > > On Mon, Mar 25, 2024 at 08:36:44AM +0100, tlaro...@kergis.com wrote: > > > In a previous mail, I proposed, when autotools and meson are both > > > provided to

Re: CI/yaml: inlining or providing an "upstream" utility

2024-03-25 Thread tlaronde
On Mon, Mar 25, 2024 at 08:07:24PM +1000, Peter Hutterer wrote: > On Mon, Mar 25, 2024 at 08:36:44AM +0100, tlaro...@kergis.com wrote: > > In a previous mail, I proposed, when autotools and meson are both > > provided to build a module, to not verify what they provide by simply > > diffing the

Re: CI/yaml: inlining or providing an "upstream" utility

2024-03-25 Thread Peter Hutterer
On Mon, Mar 25, 2024 at 08:36:44AM +0100, tlaro...@kergis.com wrote: > In a previous mail, I proposed, when autotools and meson are both > provided to build a module, to not verify what they provide by simply > diffing the resulting installation directories, but to treat pkgconfig > generated *.pc

CI/yaml: inlining or providing an "upstream" utility

2024-03-25 Thread tlaronde
In a previous mail, I proposed, when autotools and meson are both provided to build a module, to not verify what they provide by simply diffing the resulting installation directories, but to treat pkgconfig generated *.pc files specially, by comparing them semantically and not lexically (just