On 02/09/17 23:55, Carsten Haitzler (The Rasterman) wrote:
> On Sat, 2 Sep 2017 12:53:05 +0930 Simon Lees <sfl...@suse.de> said:
> 
>>
>>
>> On 02/09/17 10:51, Carsten Haitzler (The Rasterman) wrote:
>>> On Fri, 1 Sep 2017 20:38:59 +0200 marcel-hollerb...@t-online.de said:
>>>
>>>> On Fri, Sep 01, 2017 at 08:07:18PM +0200, Davide Andreoli wrote:
>>>>> 2017-09-01 19:50 GMT+02:00 Mike Blumenkrantz
>>>>> <michael.blumenkra...@gmail.com
>>>>>> :
>>>>>
>>>>>> It seems that the two build systems have fallen out of sync far faster
>>>>>> than I expected, and the autotools build is both no longer functional and
>>>>>> cannot provide a dist which is able to build using meson.
>>>>>>
>>>>>> I'm not particularly interested in putting in even more work to try and
>>>>>> maintain something which is pending removal, so if anyone is super
>>>>>> interested in keeping it for the E22 release then patches are welcome,
>>>>>> otherwise I'll plan to remove autotools entirely next week before
>>>>>> starting the official release cycle.
>>>>>>
>>>>>
>>>>> +1
>>>>>
>>>>
>>>> +1
>>>>
>>>> Just probebly checking if meson versions etc. fit the most distros, so
>>>> we dont leave users behind.
>>>
>>> i think then autogen.sh should do what rage does and do a meson build setup
>>> and fix appropriate INSTALL files etc. for how to build...
>>>
>>> but we also should get some decent testing across multiple OS's like
>>> freebsd, openbsd (i know netstar maintains these as running systems ! :)).
>>> to ensure at least on a lot of targets it builds right. package maintainers
>>> too would be really fantastic if they could switch and test there too in
>>> package build env's
>>>
>>
>> Speaking with a distro maintainers hat on, for this to be usable there
>> needs to be considerably more documentation, neither meson --help,
>> README or README.wayland tell me how to enable or disable building with
>> git. All that stuff simply should be there before you get distro's to
>> try it (or intend to remove autotools) otherwise your just wasting our
>> time. Equally the html documentation is not built automatically and
>> there is no indication of how one might build it.
> 
> copying the above docs over and autogen.sh over would solve that. i can do it
> now if you want... but it's mean autogen is now meson not autofoo so autofoo
> build will effectively be disabled for most people.
> 

If meson --help listed the supported set of build flags that would be a
good starting point and likely good enough for me atleast but as of when
I wrote the email there was nothing which is annoying.

>> As a side note, git is also required for building (which wasn't the case
>> before).
> 
> that is actually incorrect. git is required to create the dist tarball only.
>

Git is required because if you try and do a build on a VM or chroot
without git installed meson will complain that git is not installed,
whether its used or not is another question but currently the e build
requires it. I'm not saying that its bad to need it its just another
change distro packagers should be aware of.

-- 

Simon Lees (Simotek)                            http://simotek.net

Emergency Update Team                           keybase.io/simotek
SUSE Linux                           Adelaide Australia, UTC+10:30
GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to