[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cairo
Subject:    Re: [cairo] Release management for Cairo
From:       Emmanuele Bassi <ebassi () gmail ! com>
Date:       2021-04-26 11:53:04
Message-ID: CALnHYQGDj+Ep8Rk+n3AjnbLDqxAqDt8x5aMYu7qH2o0OdO4v7Q () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi;

On Sun, 25 Apr 2021 at 23:56, Dave Yeo <dave.r.yeo@gmail.com> wrote:


> As an OS/2 user, it would be a shame to see the os2surface dropped,
> though I do notice that currently "yum info cairo" reports that it is
> version 1.12.18 that ships with current OS/2.
>

Just for context: Cairo 1.12.18 was released in 2012.


> It is understandable about the maintenance burden, and currently we
> don't have meson support and meson seems pretty rigid so adding support
> would be non-trivial from a quick look, especially as OS/2 (actually
> ArcOS, www.arcanoae.com) currently only ships Python2.
>

Yes, the dependency on Meson alone would require depending on Python3,
which is why the OS/2 (and BeOS) support is unconditionally disabled in the
Meson build.

I do think that even after backporting any relevant fixes to the 1.16
> branch, it should be left open for other fixes. I maintain a few parts
> of OS/2 such as the screensaver which uses Cairo for some modules and
> have patches that should be applied. I haven't posted them due to the
> lack of maintainer-ship amongst other reasons.
>

Keeping 1.16 open for long-term, niche platform fixes is perfectly fine.

Ciao,
 Emmanuele.

-- 
https://www.bassi.io
[@] ebassi [@gmail.com]

[Attachment #5 (text/html)]

<div dir="ltr"><div>Hi;</div><div><br></div><div dir="ltr">On Sun, 25 Apr 2021 at \
23:56, Dave Yeo &lt;<a \
href="mailto:dave.r.yeo@gmail.com">dave.r.yeo@gmail.com</a>&gt; wrote:<br></div><div \
class="gmail_quote"><div>  </div><blockquote class="gmail_quote" style="margin:0px \
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> As an OS/2 \
user, it would be a shame to see the os2surface dropped, <br> though I do notice that \
currently &quot;yum info cairo&quot; reports that it is <br> version 1.12.18 that \
ships with current OS/2.<br></blockquote><div><br></div><div>Just for context: Cairo \
1.12.18 was released in 2012.<br></div><div>  </div><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> It is understandable about the maintenance \
burden, and currently we <br> don&#39;t have meson support and meson seems pretty \
rigid so adding support <br> would be non-trivial from a quick look, especially as \
OS/2 (actually <br> ArcOS, <a href="http://www.arcanoae.com" rel="noreferrer" \
target="_blank">www.arcanoae.com</a>) currently only ships \
Python2.<br></blockquote><div><br></div><div>Yes, the dependency on Meson alone would \
require depending on Python3, which is why the OS/2 (and BeOS) support is \
unconditionally disabled in the Meson build.</div><div><br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> I do think that even after backporting any \
relevant fixes to the 1.16 <br> branch, it should be left open for other fixes. I \
maintain a few parts <br> of OS/2 such as the screensaver which uses Cairo for some \
modules and <br> have patches that should be applied. I haven&#39;t posted them due \
to the <br> lack of maintainer-ship amongst other reasons.<br \
clear="all"></blockquote><div><br></div><div>Keeping 1.16 open for long-term, niche \
platform fixes is perfectly fine.</div><div><br></div><div>Ciao,</div><div>  \
Emmanuele.<br></div></div><br>-- <br><div dir="ltr" class="gmail_signature"><a \
href="https://www.bassi.io" target="_blank">https://www.bassi.io</a><br>[@] ebassi \
[@<a href="http://gmail.com" target="_blank">gmail.com</a>]</div></div>



-- 
cairo mailing list
cairo@cairographics.org
https://lists.cairographics.org/mailman/listinfo/cairo


[prev in list] [next in list] [prev in thread] [next in thread]