On Sunday, 9 December 2018 at 16:53:22 UTC, Filipe Laíns wrote:
> On Thursday, 6 December 2018 at 13:10:53 UTC, Basile B. wrote:
>> If i remember correctly the idea behind the addition of Meson build files was to have some semi official packages for D-scanner and DCD. Where are they ?
>>
>> Right now I'm a bit angry because of the maintenance required to support Meson. Usually i just don't care but today the CI is broken for some reasons (i just know it's related to Meson support. And this is not the first time.
>
> If you want I can step in and maintain meson. Also, we have official package for both D-Scanner and DCD in Archlinux.

I'm thinking about inviting you to dlang-community then. Do you think you can fix at least the stupid stuff we have to do right know (install python 3 while it's already setup). Again today i have to do this:

    https://github.com/dlang-community/tinyendian/pull/18/files

Which is awfully slow. Most of the time is spent on setup python 3.6.3, which is not correct. CI tests for this product should not spend more than 30 secs. Now they raise to 4 minutes.

The problem right now is that i handle this while i should not. I have zero python+its ecosystem knowledge, i just use "dub" "make" or my own exotic way of building, so the fix has chances to be be stupid.

On Wednesday, 12 December 2018 at 12:23:40 UTC, Basile B. wrote:
> On Sunday, 9 December 2018 at 16:53:22 UTC, Filipe Laíns wrote:
>> On Thursday, 6 December 2018 at 13:10:53 UTC, Basile B. wrote:
>>> If i remember correctly the idea behind the addition of Meson build files was to have some semi official packages for D-scanner and DCD. Where are they ?
>>>
>>> Right now I'm a bit angry because of the maintenance required to support Meson. Usually i just don't care but today the CI is broken for some reasons (i just know it's related to Meson support. And this is not the first time.
>>
>> If you want I can step in and maintain meson. Also, we have official package for both D-Scanner and DCD in Archlinux.
>
> I'm thinking about inviting you to dlang-community then. Do you think you can fix at least the stupid stuff we have to do right know (install python 3 while it's already setup). Again today i have to do this:
>
>     https://github.com/dlang-community/tinyendian/pull/18/files
>
> Which is awfully slow. Most of the time is spent on setup python 3.6.3, which is not correct. CI tests for this product should not spend more than 30 secs. Now they raise to 4 minutes.
>
> The problem right now is that i handle this while i should not. I have zero python+its ecosystem knowledge, i just use "dub" "make" or my own exotic way of building, so the fix has chances to be be stupid.

Just 3 minutes to install a python version at Travis, that will work to use Meson

    https://travis-ci.org/dlang-community/tinyendian/jobs/466966513#L122

That's **silly**.

On Wednesday, 12 December 2018 at 12:40:35 UTC, Basile B. wrote:
> Just 3 minutes to install a python version at Travis, that will work to use Meson
>
>     https://travis-ci.org/dlang-community/tinyendian/jobs/466966513#L122
>
> That's **silly**.

What's even more silly is building Python manually first, then doing `homebrew update` (taking 290 secs!) before brewing ninja and Python again (the latter not working). If you just need homebrew for Ninja, then do yourself a favor and download the prebuilt https://github.com/ninja-build/ninja/releases/download/v1.8.2/ninja-mac.zip, that's what we do for LDC CI too. This `homebrew update` is ridiculous, at least for Travis.

On Wednesday, 12 December 2018 at 12:23:40 UTC, Basile B. wrote:
>
> I'm thinking about inviting you to dlang-community then. Do you think you can fix at least the stupid stuff we have to do right know (install python 3 while it's already setup). Again today i have to do this:
>
>     https://github.com/dlang-community/tinyendian/pull/18/files
>
> Which is awfully slow. Most of the time is spent on setup python 3.6.3, which is not correct. CI tests for this product should not spend more than 30 secs. Now they raise to 4 minutes.
>
> The problem right now is that i handle this while i should not. I have zero python+its ecosystem knowledge, i just use "dub" "make" or my own exotic way of building, so the fix has chances to be be stupid.

That's fine by me. I may not be as active as I would wish at times so if that happens just give me a mention or send me an email.

Regarding your issue, it seems that meson 0.29.0 is available in xenial's repo so that might be worth installing directly. To avoid installing python each CI run, you might want to cache it[1]. That should speed up the CI quite a bit.

[1] https://docs.travis-ci.com/user/caching/

On Saturday, 15 December 2018 at 00:47:34 UTC, Filipe Laíns wrote:
> On Wednesday, 12 December 2018 at 12:23:40 UTC, Basile B. wrote:
>>
>> I'm thinking about inviting you to dlang-community then. Do you think you can fix at least the stupid stuff we have to do right know (install python 3 while it's already setup). Again today i have to do this:
>>
>>     https://github.com/dlang-community/tinyendian/pull/18/files
>>
>> Which is awfully slow. Most of the time is spent on setup python 3.6.3, which is not correct. CI tests for this product should not spend more than 30 secs. Now they raise to 4 minutes.
>>
>> The problem right now is that i handle this while i should not. I have zero python+its ecosystem knowledge, i just use "dub" "make" or my own exotic way of building, so the fix has chances to be be stupid.
>
> That's fine by me. I may not be as active as I would wish at times so if that happens just give me a mention or send me an email.
>
> Regarding your issue, it seems that meson 0.29.0 is available in xenial's repo so that might be worth installing directly. To avoid installing python each CI run, you might want to cache it[1]. That should speed up the CI quite a bit.
>
> [1] https://docs.travis-ci.com/user/caching/

I didn't know that meson 0.29 is available on their xenial-based VMs but i was adviced yesterday to use xenial because it has python 3.5 which is good enough for meson. This is what i did, everywhere([1],[2],...), so everything is fine now.

By the way meson 0.29 is probably not capable of building D. This looks like a very old release.

[1] https://github.com/dlang-community/libdparse/pull/332/files
[2] https://github.com/dlang-community/containers/pull/132/files

On Thursday, 6 December 2018 at 10:54:48 UTC, Basile B. wrote:
> Do you use it ? Is it useful ?

At Fedora we use meson to build these projects. So yes it is useful

Debian uses meson to build things D as well and it appears to fit elegantly with their package creation tools, related work is already in place. Fedora it appears uses meson too. My understanding use of meson integrates with the rest of Debian package creation system and more or less automates the process... anything to make use of meson more straightforward makes the packaging and distribution of D tools, libraries and applications more likely, and should be positive with regard to the adoption of things D within Linux infrastructure (Debian + its many derivatives and Red Hat / Fedora). Reiteration of previous post. More with meson (and to assist its use with things D) please, not less.

(reiteration of earlier posts:)
https://github.com/mesonbuild/meson/pull/685
https://forum.dlang.org/post/ezwgtwhrmxtggejboogn@forum.dlang.org
https://forum.dlang.org/post/dpakidboblzgbdtejilz@forum.dlang.org
https://forum.dlang.org/post/wfzvzberakgfvdspqzro@forum.dlang.org
https://forum.dlang.org/post/gafxocanzszlqrrofcjw@forum.dlang.org
https://forum.dlang.org/post/mailman.1087.1482453335.9448.digitalmars-d-bugs@puremagic.com


On Mon, Dec 17, 2018 at 4:20 AM bioinfornatics via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
>
> On Thursday, 6 December 2018 at 10:54:48 UTC, Basile B. wrote:
> > Do you use it ? Is it useful ?
>
> At Fedora we use meson to build these projects. So yes it is useful

On Saturday, 15 December 2018 at 04:55:53 UTC, Basile B. wrote:
> I didn't know that meson 0.29 is available on their xenial-based VMs but i was adviced yesterday to use xenial because it has python 3.5 which is good enough for meson. This is what i did, everywhere([1],[2],...), so everything is fine now.
>
> By the way meson 0.29 is probably not capable of building D. This looks like a very old release.
>
> [1] https://github.com/dlang-community/libdparse/pull/332/files
> [2] https://github.com/dlang-community/containers/pull/132/files

Sorry for the super late reply! I have been really busy with the holidays.

At the time I didn't realize meson 0.29 was **that** outdated. If we cache the package contents' meson doesn't need to be installed on each CI run.

I'll try to open some pull requests with this hopefully working.