You are not logged in.
Pages: 1


Currently i run pools to understand , what most desktop Linux users prefer or use daily as X Server, there many options right now , but i can do integrate only one into my distribution.
I would like if you can participate at the pools:
THANKS IN ADVANCE !
Offline


I use x.org, but I would gladly transition to Wayland protocol if XFCE had a Wayland compositor.
Anyway, regarding T2 Linux and its package manager: I see it is based on build recipes.
My question: How does it then prevent the same fiasco that struck Arch Linux AUR, where malicious people were maintaining build recipes, and therefore they were able to plant malware into build recipes?
^^^^^ &```& ^^^^^^^^^^^^^
.&_ oO_&-..--. daffyduck
( __ -/..--' Mark solved threads as [SOLVED] to make
. ' -__- ' it easier for others to find solutions.
Offline


I use x.org, but I would gladly transition to Wayland protocol if XFCE had a Wayland compositor.
Anyway, regarding T2 Linux and its package manager: I see it is based on build recipes.
My question: How does it then prevent the same fiasco that struck Arch Linux AUR, where malicious people were maintaining build recipes, and therefore they were able to plant malware into build recipes?
Let me clarify, i am not developer of T2 Linux, i run my own custom build version , sure at the moment my distro don't look different as T2 Linux upstream itself, but it can change with time.
About preventing malicious stuff , we use CodeQL, and my policy to have always final ruling, so we don't allow unknow to us person/s to submit or merge theirs code with our recipes.
My plan by growing community, to be a definitive decider and when time comes for better decision policy only then bring some new orga into the community.
So XFCE doesn't have working Wayland compositor, hm that a big minus for me in favor of XLibre.
IF you want to know about my project, visit https://orlovskyjavaprofi.github.io thats were i put general info about my distro.
Last edited by aorlovsky (2026-07-19 17:26:43)
Offline


A wayland compositor is being worked on right now. It maybe a while before we see a release. You can download a test build but don't expect much. As of right now you can use either Wayfire or Labwc. Both are good choices right now and mostly function well with Xfce. There are a few glitches though. I have Labwc installed but only use on occasion.
But it's all right, when you're all in pain and you feel the rain come down
It's alright, when you find your way, then you see it disappear
It's alright....
Chris Cornell
Offline


About preventing malicious stuff , we use CodeQL, and my policy to have always final ruling, so we don't allow unknow to us person/s to submit or merge theirs code with our recipes.
At least, does every recipe use a cryptographically secure checksum for its downloads?
For downloads, do ALL recipes use crypto hashes, or MOST, or just SOME?
Because, I want "ALL", but I suspect that is only "SOME" in the current T2 repository recipes.
^^^^^ &```& ^^^^^^^^^^^^^
.&_ oO_&-..--. daffyduck
( __ -/..--' Mark solved threads as [SOLVED] to make
. ' -__- ' it easier for others to find solutions.
Offline


A wayland compositor is being worked on right now. It maybe a while before we see a release. You can download a test build but don't expect much. As of right now you can use either Wayfire or Labwc. Both are good choices right now and mostly function well with Xfce. There are a few glitches though. I have Labwc installed but only use on occasion.
That is promising, maybe we can collaborate and i can help and boost the development in this direction.
Added later 01 min 06 s:
aorlovsky wrote:About preventing malicious stuff , we use CodeQL, and my policy to have always final ruling, so we don't allow unknow to us person/s to submit or merge theirs code with our recipes.
At least, does every recipe use a cryptographically secure checksum for its downloads?
For downloads, do ALL recipes use crypto hashes, or MOST, or just SOME?
Because, I want "ALL", but I suspect that is only "SOME" in the current T2 repository recipes.
Every package in T2 Linux have sha256 checksum, dont worry everything is audited.
Offline


More information HERE.
But it's all right, when you're all in pain and you feel the rain come down
It's alright, when you find your way, then you see it disappear
It's alright....
Chris Cornell
Offline


Every package in T2 Linux have sha256 checksum, dont worry everything is audited.
No, it doesn't.
Like, this one doesn't have a cryptographicaly secure checksum:
https://svn.exactcode.de/t2/trunk/packa … erium.desc
But, I admit, it is about twentieth package I checked, so I guess that MOST downloads have checksums.
Edit: I noticed that checksums are 28 bytes long, instead of the usual 32 bytes. For security, the difference is irrelevant. But, 28 bytes can be confusing for some people. So: why are checksums not the usual 32 bytes ?
Added later 14 min 40 s:
More information HERE.
Labwc compositor looks quite acceptable to me ... if it generally works and integrates well. I guess no Xfwm keyboard shortcuts with Labwc, so the user is forced to re-configure at least the keyboard shortcuts.
And with Labwc, you have to cross your fingers that panels and panel plugins work properly (do they?). Even on Xorg, there were bugs: panel notification taking up 100% CPU time, or blinking. Or (in 4.16) application not starting due to panel tray icon issues.
And, the SUPER-combo shortcuts have not been working properly in XFCE since long time ago ... but there is a workaround for that, albeit complicated. Or maybe it was finally patched in 4.20 ? I mean: the ability to detect SUPER key press-release (in global shortcuts) separately from SUPER-combos (for Xfwm4).
But, I still have high hopes for Xfwl4.
Last edited by daffyduck (2026-07-19 23:35:35)
^^^^^ &```& ^^^^^^^^^^^^^
.&_ oO_&-..--. daffyduck
( __ -/..--' Mark solved threads as [SOLVED] to make
. ' -__- ' it easier for others to find solutions.
Offline


Folks , so i have found info about what to consider about Wayland , here look at possible issues.
What Wayland sells is theirs more "superior" architecture, allowing them to implement and fix bugs faster, that's for me and i am starting considering Wayland as defacto X-Server for my distro, but the pools are not done yet, i need more feedback on that:
https://x.com/OrlConsultGbR/status/2078537990708560017
https://mastodon.social/@orlovskyconsul … 9603168304
https://github.com/orlovskyjavaprofi/t2 … ussions/31
Last edited by aorlovsky (2026-07-21 15:17:53)
Offline


What Wayland sells is theirs more "superior" architecture,
Superior? I'm pretty certain that any network-transparent protocol is a priori architecturally superior to one that is not. Well, many X11 extensions are not network-transparent, but that's still better than Wayland.
On the other side, having central "Wayland-compositor" service is certainly a good idea, definitively better then the X11 mess-of-services.
Wayland is also more secure, while X11 is essentially insecure.
So, a mixed bag there, some improvements, some regressions.
allowing them to implement and fix bugs faster, that's for me and i am starting considering Wayland as defacto X-Server for my distro, but the pools are not done yet, i need more feedback on that:
The problem with X11 is that it is old, messy and complicated, so it was hard to fix bugs, but that has nothing to do with the architecture.
As for Wayland, in the future you will have no choice, because all major distros will move to Wayland.
Currently you can still choose between X11 and Wayland, but in 10 years the majority of modern applications will probably be broken on X11.
Your pool only makes sense in the near future, perhaps one year into the future. After that, the usage patterns are likely to switch towards Wayland.
But, at the present, X11 is still viable, of course. I'm also not using Wayland yet.
Added later 20 min 06 s:
Putting too many exclamations marks everywhere makes you look very unprofessional. English guidelines discourage such usage.
Also, you have put most of the body text as headings (<h2>) tag. That's also unprofessional.
Also, you use too much ALL-CAPS.
Current recommendation for body font size is 17px to 21px, while on your page the text is 24px large.
So... your page looks odd, to say it mildly. I would guess that most people won't take you seriously.
Furthermore, when you offer an ISO for download, you should specify the ISA (i.e. x86-64).
For even more professionalism, write instructions for a reproducible build, so that anyone can verify that your ISO is truly created from declared sources.
Last edited by daffyduck (2026-07-20 18:27:17)
^^^^^ &```& ^^^^^^^^^^^^^
.&_ oO_&-..--. daffyduck
( __ -/..--' Mark solved threads as [SOLVED] to make
. ' -__- ' it easier for others to find solutions.
Offline


That "post work" which you mentioned is for volunteers only , in my opinion it is perfect as is, everyone has own "measuring tape", and i understand it may look strange , but this is how most opensource projects run this days.
Everything else you can find in WIKI.
Last edited by aorlovsky (2026-07-21 15:20:41)
Offline
Pages: 1
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 605.02 KiB (Peak: 637.99 KiB) ]