From: Jens Axboe <axboe@kernel.dk>
To: Martin Steigerwald <martin@lichtvoll.de>, fio@vger.kernel.org
Subject: Re: gfio and GTK-3
Date: Wed, 26 Jul 2023 07:07:17 -0600 [thread overview]
Message-ID: <2a66e6aa-f6df-2623-5500-5115f202ca85@kernel.dk> (raw)
In-Reply-To: <1950739.PYKUYFuaPT@lichtvoll.de>
On 7/26/23 2:47?AM, Martin Steigerwald wrote:
> Hi Jens.
>
> Jens Axboe - 20.08.20, 13:52:40 CEST:
>> On 8/20/20 1:43 AM, Martin Steigerwald wrote:
>>> Is gfio compatible with GTK-3?
>>>
>>> I am asking due to Debian wanting to get rid of GTK-2 at some time:
>>>
>>> fio: depends on deprecated GTK 2: https://bugs.debian.org/967339
>>>
>>> If not, are there plans to make it compatible? Or are there plans to
>>> drop it instead?
>>
>> I'm tempted to just drop it. gfio never really got what I consider
>> finished, and I don't think it's in widespread use.
>>
>> Maybe I'm wrong and there are in fact people out there using it. I
>> know someone had a patch at some point to convert it to gtk3, and
>> if that's still the case, I would not mind applying that and making
>> it continue to live in the repo.
>
> Did anyone submit a patch for GTK-3 support in gfio?
Not too my knowledge.
> If not, I agree, probably best to just drop it. Especially after almost
> 3 years and as GTK-4 is around the corner. In case anyone would like to
> port it they can resurrect it from git history.
Yep, we probably should. Nobody has been working on it in many years. It
probably still works fine, but it's mostly just a GUI frontend and it's
still lacking features that you would want to consider it a good GUI
frontend.
--
Jens Axboe
prev parent reply other threads:[~2023-07-26 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 8:43 gfio and GTK-3 Martin Steigerwald
2020-08-20 11:52 ` Jens Axboe
2023-07-26 8:47 ` Martin Steigerwald
2023-07-26 13:07 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2a66e6aa-f6df-2623-5500-5115f202ca85@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=martin@lichtvoll.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).