Re: For projects switching to Meson *only*

The issue is not writing a simple patch: it takes me about 90 seconds
of my life to copy the file, create a commit, format-patch it, and add
the patch to gnome-continuous.

The whole point would be to avoid adding a patch to Continuous.

Additionally, conforming to the build-api is a nice transitional tool
for distributors that are still trying to catch up to Meson.


On 27 April 2017 at 09:48, Carlos Soriano <csoriano protonmail com> wrote:
Hello Emmanuele,

Would be fine if the maintainer does the patch for continuous instead of
doing the build-API?

Carlos Soriano

-------- Original Message --------
Subject: For projects switching to Meson *only*
Local Time: 27 April 2017 10:45 AM
UTC Time: 27 April 2017 08:45
From: ebassi gmail com
To: Desktop Development List <desktop-devel-list gnome org>

Hi everyone;

since maintainers have started switching to Meson for the development
cycle (awesome!) I'd like to ask for a favour: if you're dropping
autotools entirely, could you please add a `configure` wrapper script
that conforms to the build-api[1] that GNOME Continuous uses?

A simple script is available here[2], and it has nice properties, like
being able to work with a simple:

sudo make install

which makes distributors and integrators happy.

Before you ask: yes, I'm looking at adding Meson support to
Continuous, as part of a larger rework of the manifest file to adapt
to the Flatpak builder manifest format; that will take time, though,
so in the interim it'd be great if we didn't have to ship a patch for
every project, when the alternative is simply dropping a script into
the project's top-level.



[@] ebassi []
desktop-devel-list mailing list
desktop-devel-list gnome org

[@] ebassi []

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]