On Tuesday, February 7, 2017 9:23:22 AM EST William Hubbs wrote:
> On Tue, Feb 07, 2017 at 01:22:22AM +0100, Maciej Mrozowski wrote:
> > I'd recommend to jump a bandwagon and switch to CMake.
> >
> > Yes, it's ugly in certain areas, has its quirks but whoever switches to it
> > ones, never goes ba
On Tue, Feb 07, 2017 at 01:22:22AM +0100, Maciej Mrozowski wrote:
> I'd recommend to jump a bandwagon and switch to CMake.
>
> Yes, it's ugly in certain areas, has its quirks but whoever switches to it
> ones, never goes back, and not because of technical debt being too big.
>
> Also because I c
On poniedziałek, 30 stycznia 2017 14:04:06 CET William Hubbs wrote:
> All,
>
> I have been looking at the meson build system [1] [2], and I like what I
> see.
>
> I have opened an issue on OpenRC's github wrt migrating OpenRC to the
> meson build system [3].
>
> As I said on the bug, the downsid
2017-02-03 10:52 GMT+01:00 Lars Wendler :
> On Fri, 3 Feb 2017 10:32:30 +0100 Kristian Fiskerstrand wrote:
>
> >On 02/03/2017 10:10 AM, Benda Xu wrote:
> >> William Hubbs writes:
> >>
> >>> I have been looking at the meson build system [1] [2], and I like
> >>> what I see.
> >>>
> >>> I have open
On Fri, 3 Feb 2017 10:32:30 +0100 Kristian Fiskerstrand wrote:
>On 02/03/2017 10:10 AM, Benda Xu wrote:
>> William Hubbs writes:
>>
>>> I have been looking at the meson build system [1] [2], and I like
>>> what I see.
>>>
>>> I have opened an issue on OpenRC's github wrt migrating OpenRC to
>>
On 02/03/2017 10:10 AM, Benda Xu wrote:
> William Hubbs writes:
>
>> I have been looking at the meson build system [1] [2], and I like what I
>> see.
>>
>> I have opened an issue on OpenRC's github wrt migrating OpenRC to the
>> meson build system [3].
>>
>> As I said on the bug, the downside is
William Hubbs writes:
> I have been looking at the meson build system [1] [2], and I like what I
> see.
>
> I have opened an issue on OpenRC's github wrt migrating OpenRC to the
> meson build system [3].
>
> As I said on the bug, the downside is the addition of py3 and ninja as
> build time depen
On 02/01/2017 10:46 AM, William Hubbs wrote:
> On Wed, Feb 01, 2017 at 03:55:17PM +, James Le Cuirot wrote:
>> On Wed, 1 Feb 2017 09:39:34 -0600
>> William Hubbs wrote:
>>
>>> I thought about autotools. I'm not really fond of its syntax, and I've
>>> been told that, to use autotools correctl
On 02/01/2017 08:53 AM, Ian Stakenvicius wrote:
> On 01/02/17 09:43 AM, William Hubbs wrote:
>> On Wed, Feb 01, 2017 at 01:18:42PM +0100, Michał Górny wrote:
>>> W dniu 30.01.2017, pon o godzinie 14∶04 -0600, użytkownik William Hubbs
>>> napisał:
All,
I have been looking at the meson
On Wed, Feb 01, 2017 at 12:25:37PM -0500, james wrote:
> On 02/01/2017 10:40 AM, William Hubbs wrote:
> > On Wed, Feb 01, 2017 at 01:37:04AM +, Robin H. Johnson wrote:
> >> On Mon, Jan 30, 2017 at 02:04:06PM -0600, William Hubbs wrote:
> >>> As I said on the bug, the downside is the addition of
On Wed, Feb 01, 2017 at 09:03:49AM -0600, William Hubbs wrote:
> On Wed, Feb 01, 2017 at 11:54:41AM +0100, Tobias Klausmann wrote:
> > Hi!
> >
> > On Mon, 30 Jan 2017, William Hubbs wrote:
> > > I have been looking at the meson build system [1] [2], and I like what I
> > > see.
> > >
> > > I hav
On 01/02/17 10:39 AM, William Hubbs wrote:
>
> I thought about autotools. I'm not really fond of its syntax, and I've
> been told that, to use autotools correctly, I would need to start
> generating manual release tarballs again because I would need to put the
> autotools generated cruft in them.
On 02/01/2017 10:39 AM, William Hubbs wrote:
On Wed, Feb 01, 2017 at 01:37:04AM +, Robin H. Johnson wrote:
On Mon, Jan 30, 2017 at 02:04:06PM -0600, William Hubbs wrote:
As I said on the bug, the downside is the addition of py3 and ninja as
build time dependencies, but I think the upside (a
On 02/01/2017 10:40 AM, William Hubbs wrote:
On Wed, Feb 01, 2017 at 01:37:04AM +, Robin H. Johnson wrote:
On Mon, Jan 30, 2017 at 02:04:06PM -0600, William Hubbs wrote:
As I said on the bug, the downside is the addition of py3 and ninja as
build time dependencies, but I think the upside (a
On Mon, Jan 30, 2017 at 03:08:42PM -0600, Dustin C. Hatch wrote:
> On 2017-01-30 14:04, William Hubbs wrote:
> > I have opened an issue on OpenRC's github wrt migrating OpenRC to the
> > meson build system [3].
> >
> > …
> >
> > What do folks think here?
> >
>
> I looked at Meson a bit, and I l
On Wed, 1 Feb 2017 10:46:12 -0600
William Hubbs wrote:
> On Wed, Feb 01, 2017 at 03:55:17PM +, James Le Cuirot wrote:
> > On Wed, 1 Feb 2017 09:39:34 -0600
> > William Hubbs wrote:
> >
> > > I thought about autotools. I'm not really fond of its syntax, and
> > > I've been told that, to us
On Wed, Feb 01, 2017 at 03:55:17PM +, James Le Cuirot wrote:
> On Wed, 1 Feb 2017 09:39:34 -0600
> William Hubbs wrote:
>
> > I thought about autotools. I'm not really fond of its syntax, and I've
> > been told that, to use autotools correctly, I would need to start
> > generating manual rele
On Wed, 1 Feb 2017 09:39:34 -0600
William Hubbs wrote:
> I thought about autotools. I'm not really fond of its syntax, and I've
> been told that, to use autotools correctly, I would need to start
> generating manual release tarballs again because I would need to put
> the autotools generated cruf
On Wed, Feb 01, 2017 at 01:37:04AM +, Robin H. Johnson wrote:
> On Mon, Jan 30, 2017 at 02:04:06PM -0600, William Hubbs wrote:
> > As I said on the bug, the downside is the addition of py3 and ninja as
> > build time dependencies, but I think the upside (a build system where
> > we don't have t
On Wed, Feb 01, 2017 at 11:54:41AM +0100, Tobias Klausmann wrote:
> Hi!
>
> On Mon, 30 Jan 2017, William Hubbs wrote:
> > I have been looking at the meson build system [1] [2], and I like what I
> > see.
> >
> > I have opened an issue on OpenRC's github wrt migrating OpenRC to the
> > meson buil
On 01/02/17 09:43 AM, William Hubbs wrote:
> On Wed, Feb 01, 2017 at 01:18:42PM +0100, Michał Górny wrote:
>> W dniu 30.01.2017, pon o godzinie 14∶04 -0600, użytkownik William Hubbs
>> napisał:
>>> All,
>>>
>>> I have been looking at the meson build system [1] [2], and I like
>>> what I
>>> see.
>>
On Wed, Feb 01, 2017 at 01:18:42PM +0100, Michał Górny wrote:
> W dniu 30.01.2017, pon o godzinie 14∶04 -0600, użytkownik William Hubbs
> napisał:
> > All,
> >
> > I have been looking at the meson build system [1] [2], and I like
> > what I
> > see.
> >
> > I have opened an issue on OpenRC's gith
W dniu 30.01.2017, pon o godzinie 14∶04 -0600, użytkownik William Hubbs
napisał:
> All,
>
> I have been looking at the meson build system [1] [2], and I like
> what I
> see.
>
> I have opened an issue on OpenRC's github wrt migrating OpenRC to the
> meson build system [3].
>
> As I said on the b
Hi!
On Mon, 30 Jan 2017, William Hubbs wrote:
> I have been looking at the meson build system [1] [2], and I like what I
> see.
>
> I have opened an issue on OpenRC's github wrt migrating OpenRC to the
> meson build system [3].
>
> As I said on the bug, the downside is the addition of py3 and n
On Tue, Jan 31, 2017 at 9:29 PM, Kent Fredric wrote:
>
> And we should be keeping the @system essentials set required for new
> installations
> to be as minimal as possible without losing functionality.
>
Keep in mind that it is pretty safe to put openrc in package.provided,
well, as long as you
On Mon, 30 Jan 2017 14:04:06 -0600
William Hubbs wrote:
> As I said on the bug, the downside is the addition of py3 and ninja as
> build time dependencies, but I think the upside (a build system where
> we don't have to worry about parallel make issues or portability)
> outweighs that.
On princi
On Mon, Jan 30, 2017 at 02:04:06PM -0600, William Hubbs wrote:
> As I said on the bug, the downside is the addition of py3 and ninja as
> build time dependencies, but I think the upside (a build system where
> we don't have to worry about parallel make issues or portability)
> outweighs that.
Could
On Mon, Jan 30, 2017 at 12:04 PM, William Hubbs wrote:
> All,
>
> I have been looking at the meson build system [1] [2], and I like what I
> see.
>
> I have opened an issue on OpenRC's github wrt migrating OpenRC to the
> meson build system [3].
>
> As I said on the bug, the downside is the additi
On 01/30/2017 15:04, William Hubbs wrote:
> All,
>
> I have been looking at the meson build system [1] [2], and I like what I
> see.
>
> I have opened an issue on OpenRC's github wrt migrating OpenRC to the
> meson build system [3].
>
> As I said on the bug, the downside is the addition of py3 a
On 2017-01-30 14:04, William Hubbs wrote:
> I have opened an issue on OpenRC's github wrt migrating OpenRC to the
> meson build system [3].
>
> …
>
> What do folks think here?
>
I looked at Meson a bit, and I liked almost everything, except the
configuration file-based mechanism for cross-compi
On Mon, 30 Jan 2017 14:04:06 -0600
William Hubbs wrote:
> I have been looking at the meson build system [1] [2], and I like what I
> see.
I've still only read the documentation but I agree with your
assessment. It's nice to hear something positive about a build system
for once.
> As I said on t
All,
I have been looking at the meson build system [1] [2], and I like what I
see.
I have opened an issue on OpenRC's github wrt migrating OpenRC to the
meson build system [3].
As I said on the bug, the downside is the addition of py3 and ninja as
build time dependencies, but I think the upside
32 matches
Mail list logo
