On Mon, 21 Aug 2017 18:17:27 + Mike Blumenkrantz
said:
> This is irrelevant; git archive packages all files tracked by git, meaning
> that autotools build works as expected. Platforms that we haven't done
> testing for can just be advised to continue using autotools.
it's not irrelevant. it
On Mon, 21 Aug 2017 16:44:26 +0100 Al Poole said:
> Here, this builds E w/meson on FreeBSD...
>
> https://phab.enlightenment.org/D5112
well.. until it became an edi patch... :)
> On Mon, Aug 21, 2017 at 3:37 PM, Carsten Haitzler
> wrote:
>
> > On Mon, 21 Aug 2017 13:17:55 + Mike Blumenkr
This is irrelevant; git archive packages all files tracked by git, meaning
that autotools build works as expected. Platforms that we haven't done
testing for can just be advised to continue using autotools.
On Mon, Aug 21, 2017 at 10:37 AM Carsten Haitzler
wrote:
> On Mon, 21 Aug 2017 13:17:55 +
Here, this builds E w/meson on FreeBSD...
https://phab.enlightenment.org/D5112
On Mon, Aug 21, 2017 at 3:37 PM, Carsten Haitzler
wrote:
> On Mon, 21 Aug 2017 13:17:55 + Mike Blumenkrantz
> said:
>
> > I think for this release cycle I am going to try using the meson build
> > (which uses gi
On Mon, 21 Aug 2017 13:17:55 + Mike Blumenkrantz
said:
> I think for this release cycle I am going to try using the meson build
> (which uses git archive) so that packagers and users can decide which build
> system they prefer. This ensures that there will be no mishaps related to
> EXTRA_DIS
I think for this release cycle I am going to try using the meson build
(which uses git archive) so that packagers and users can decide which build
system they prefer. This ensures that there will be no mishaps related to
EXTRA_DIST while still allowing autotools to be used where desired.
On Fri, A
Hi,
I thought it would be clear from the content of my original mail, but
perhaps I should have been more explicit. This release cycle will be
identical to every previous release cycle except that there will no no code
freeze. There will still be pre-releases, there will still be packaging
tests o
On Sat, 19 Aug 2017 15:34:56 +0930 Simon Lees said:
>
>
> On 19/08/17 11:22, Carsten Haitzler (The Rasterman) wrote:
> > On Fri, 18 Aug 2017 20:29:47 + Mike Blumenkrantz
> > said:
> >
> > meson or autofoo build by default?
>
> Personally given how recently meson was added from a packagin
On Sat, Aug 19, 2017 at 7:04 AM, Simon Lees wrote:
>
>
> On 19/08/17 11:22, Carsten Haitzler (The Rasterman) wrote:
>> On Fri, 18 Aug 2017 20:29:47 + Mike Blumenkrantz
>> said:
>>
>> meson or autofoo build by default?
>
> Personally given how recently meson was added from a packaging and
> re
On 19/08/17 11:22, Carsten Haitzler (The Rasterman) wrote:
> On Fri, 18 Aug 2017 20:29:47 + Mike Blumenkrantz
> said:
>
> meson or autofoo build by default?
Personally given how recently meson was added from a packaging and
releasing standard i'd prefer to keep autotools for e22, maybe onc
On Fri, 18 Aug 2017 20:29:47 + Mike Blumenkrantz
said:
meson or autofoo build by default?
> Hi,
>
> Given that the 1.20 release has gone out, the main features for the release
> are long done, and there are no serious bug reports outstanding, I'm
> planning to begin the release process for
No, there will be a migration wizard which handles this automatically.
On Fri, 18 Aug 2017 22:54:27 +
Andrew Williams wrote:
> Hi,
>
> Cheers. But don't we need a full release with all replacements available so
> people can transition over?
>
> Andy
> On Fri, 18 Aug 2017 at 23:38, Michael
haha oops wrong thread!!!
On Fri, Aug 18, 2017 at 11:56 PM, Al Poole wrote:
> You'd like all instances replaced?
>
>
> On Fri, Aug 18, 2017 at 11:54 PM, Andrew Williams
> wrote:
>
>> Hi,
>>
>> Cheers. But don't we need a full release with all replacements available
>> so
>> people can transitio
You'd like all instances replaced?
On Fri, Aug 18, 2017 at 11:54 PM, Andrew Williams
wrote:
> Hi,
>
> Cheers. But don't we need a full release with all replacements available so
> people can transition over?
>
> Andy
> On Fri, 18 Aug 2017 at 23:38, Michael Blumenkrantz <
> michael.blumenkra...@
Hi,
Cheers. But don't we need a full release with all replacements available so
people can transition over?
Andy
On Fri, 18 Aug 2017 at 23:38, Michael Blumenkrantz <
michael.blumenkra...@gmail.com> wrote:
> A lot of progress was made in moving to the new gadget system, but there's
> still more w
A lot of progress was made in moving to the new gadget system, but there's
still more work to be done: I think there are 4-5 more gadgets remaining before
gadget parity is achieved.
Ideally we'll see gadcon and shelf removed in the release after this one.
On Fri, 18 Aug 2017 22:14:28 +
Andr
Hi Mike,
Great news, thanks. Where does the transition of gadget to bryce stand in
this cycle? It would be great to know what target we're aiming for to be
module complete and then to remove the old stuff.
Cheers,
Andy
On Fri, 18 Aug 2017 at 21:31 Mike Blumenkrantz <
michael.blumenkra...@gmail.c
Hi,
Given that the 1.20 release has gone out, the main features for the release
are long done, and there are no serious bug reports outstanding, I'm
planning to begin the release process for E22 within the next couple weeks.
After the increasing success of increasingly lax code freezes surroundin
18 matches
Mail list logo
