On Wed, 2024-08-07 at 21:19 +0100, James Le Cuirot wrote:
> On Wed, 2024-08-07 at 19:39 +0200, Michał Górny wrote:
> > On Wed, 2024-08-07 at 16:52 +0100, James Le Cuirot wrote:
> > > The flags we set an a target-specific environment variable override any
> > > generic [build] flags set by the proje
On Wed, Aug 07, 2024 at 09:19:36PM +0100, James Le Cuirot wrote:
> On Wed, 2024-08-07 at 19:39 +0200, Michał Górny wrote:
> > On Wed, 2024-08-07 at 16:52 +0100, James Le Cuirot wrote:
> > > The flags we set an a target-specific environment variable override any
> > > generic [build] flags set by th
On Wed, 2024-08-07 at 19:39 +0200, Michał Górny wrote:
> On Wed, 2024-08-07 at 16:52 +0100, James Le Cuirot wrote:
> > The flags we set an a target-specific environment variable override any
> > generic [build] flags set by the project, requiring ebuilds to set these
> > themselves, which is undesi
On Wed, 2024-08-07 at 16:52 +0100, James Le Cuirot wrote:
> The flags we set an a target-specific environment variable override any
> generic [build] flags set by the project, requiring ebuilds to set these
> themselves, which is undesirable. Work around this by using tomlq to
> read the flags from
The flags we set an a target-specific environment variable override any
generic [build] flags set by the project, requiring ebuilds to set these
themselves, which is undesirable. Work around this by using tomlq to
read the flags from the config files checked by Cargo and prepending
them to our envi
Cargo turned out to be even worse at handling flags than I thought.
Target-specific flags set by projects were overriding our own, and Cargo
was bailing out when faced with merging a string of flags with an array
of flags.
After weighing up the poor set of options, I've found that it is better
to
Unfortunately, my recent cargo.eclass changes didn't fare so well, despite me
testing it on a good handful of packages. I've had to sharply change tack to
work around Cargo's shortcomings.
The first commit has the main change. I'd like to merge that very soon to put
out the immediate fire.
The se
El dom, 04-08-2024 a las 00:44 +0300, Mart Raudsepp escribió:
> On Sat, 2024-08-03 at 16:04 +0200, Pacho Ramos wrote:
> > Hello,
> >
> > The rationale is briefly explained at:
> > https://bugs.gentoo.org/910363
> >
> > As gdk-pixbuf upstream is not including support for new formats,
> > people
>
