| Newsgroups |
gmane.linux.lfs.beyond.devel |
| Message-ID |
<CAOW_YOm270cXYmN7ddaW1AJw3LFQUyrwLeN2jrLW5byJMFqvOA@mail.gmail.com> |
Em seg., 30 de jun. de 2025 às 14:20, Bruce Dubbs
<[email protected]> escreveu:
>
> On 6/30/25 1:06 AM, James Powell wrote:
> > Hello Mr Dubbs, quick question about Xorg in the BLFS book. Since the Xorg 21.x
> > release hasn't gotten any major updates other than the few CVE fixes as of late, and
> > all new developments and other bug fixes and code cleanup seem to be more active on
> > the Xlibre 25.x fork, will BLFS be transitioning to Xlibre for xserver needs in the
> > future dev books or is this being monitored to see where the project heads and
> > matures? I've noticed a few distributions packaging it already or offering it
> > outright for the curious.
> >
> > If not, is the Hints project open to accepting an Xlibre centered document for
> > installation and usage?
>
> Better to send this to blfs-dev.
>
> To answer the question, we might consider a change, but need to let Xlibre mature a
> bit and see who is using it. From what I've seen, there is a lot more effort going
> into wayland right now.
>
Adding to what Bruce said, I think it is convenient to transcript some
dialogs from the xorg mailing list.
= = = Transcription begins = = =
On 6/7/25 13:19, Felipe Contreras wrote:
> I've often heard that there's only one developer working on Xorg, and
> apparently not anymore. I want to find out if that's true.
You can easily see for yourself that's not true by looking at either the
git repos on https://gitlab.freedesktop.org/xorg or the mailing list archives
at https://lists.x.org/archives/xorg-announce/ and
https://lists.x.org/archives/xorg-commit/ (though for the latter you have
to click into the individual messages since they all show gitlab as the sender).
--
-Alan Coopersmith- alan.coopersmith at oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/solaris
= = = Transcription ends = = =
Source: <https://lists.x.org/archives/xorg/2025-June/061985.html>.
= = = Transcription begins = = =
Yes, there are some of us who can't move to Wayland. In my case FVWM is not
able to work with Wayland and FVWM2 is my Window Manager of choice. I don't
know if *I* want to do something like take over Xorg all on my own.
At Sat, 7 Jun 2025 14:19:24 -0600 Felipe Contreras <felipe.contreras
at gmail.com> wrote:
>
> Hello,
>
> I've often heard that there's only one developer working on Xorg, and
> apparently not anymore. I want to find out if that's true.
>
> I'm writing an article about the people committed to keep working on
> Xorg in the future, and if there's any I would like to ask them a few
> questions.
>
> Is there anyone who is going to keep maintaining Xorg indefinitely?
>
> Cheers.
>
--
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software -- Custom Software Services
http://www.deepsoft.com/ -- Linux Administration Services
heller at deepsoft.com -- Webhosting Services
= = = Transcription ends = = =
Source: <https://lists.x.org/archives/xorg/2025-June/061988.html>.
= = = Transcription begins = = =
Hi,
Robert Heller <heller at deepsoft.com> writes:
> Yes, there are some of us who can't move to Wayland. In my case FVWM is not
> able to work with Wayland and FVWM2 is my Window Manager of choice. I don't
> know if *I* want to do something like take over Xorg all on my own.
In my case it's the lack of virtual screens in Wayland
(xrandr --panning):
$ xrandr
Screen 0: minimum 320 x 200, current 12000 x 2800, maximum 16384 x 16384
DisplayPort-0 connected primary 12000x2800+0+0 (normal left inverted
right x axis y axis) 600mm x 340mm panning 12000x2800+0+0
3840x2160 60.00*+ 30.00
:-)
Perhaps I could help? Just don't know where to start, but it doesn't
look like a big enterprise.
There was a period in Xfree86 history when it stopped supporting panning
(for a couple of years maybe), and it was a hard experience.
--
Krzysztof "Chris" Hałasa
Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa
= = = Transcription ends = = =
Source: <https://lists.x.org/archives/xorg/2025-June/061990.html>.
= = = Transcription begins = = =
And that is the main issue with wayland.
"Very intelligent" people created a protocol plus associated tooling
and libraries and expected that community will build a new great
compositor.
But if X11 was developed for ages and polished for decades by people
who loved it, no one want to spend his time and design a new
compositor for every existing GPU
Because in this case it will be just another X11.
If you take a look on Linux there are few servers in it already - like
systemd or dbus, pulse/pipewire, named ...
For my understanding there is nothing wrong with a server/client
approach and right now there is not any evidence that there is a
wayland compositor that works like X11
Second problem that desktop must adopt such compositor.
My personal opinion is that there are some issues need to be solved
before wayland compositor can substitute X11.
So I think X11 will work for us another 5 -10 years.
= = = Transcription ends = = =
Source: <https://lists.x.org/archives/xorg/2025-June/061992.html>.
As anyone can see, the protocol named "wayland" still is very
controversial and the protocol named "X11" still is the safe and
stable choice nowadays.
Sincerely,
Jamenson Ferreira Espindula de Almeida Melo
Jaboatão dos Guararapes, Pernambuco, Brazil
GNU/Linux user #166197; LFS ID 24492
Key fingerprint: 234D 1914 4224 7C53 BD13 6855 2AE0 25C0 08A8 6180
--
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page