Openssl is necessary to run gsconnect, i bet that most folks here uses gsconnect, hence the need to layer it.
Is there any alternative to gsconnect or any way to not layer it to justify openssl not becoming bundled with SB ?
This is tracked in Add openssl to the base system · Issue #201 · fedora-silverblue/issue-tracker · GitHub
Is there any movement on it really? It’s been 3yrs and the conversations honetly seem like they all hit the wall.
This issue is very old, i dont think it will help on this.
But Ravier is the right guy to the job. Do you think is possible bro, to make this happens ?
Yes it’s possible but someone has to do the work.
As much as possible, we don’t want to diverge in Silverblue from the package set that is in Fedora Workstation, thus we prefer to first ask Workstation if they want to consider adding that package to their default package set: Add openssl to the base system · Issue #201 · fedora-silverblue/issue-tracker · GitHub
If they accept then it’s easy, we just sync with what they do.
If they refuse, then we need to decide for ourselves. As we can not just add any package that is being requested without at least considering the size, all new packages should go through the “Add new package” issue template, that has to be dully completed: Sign in to GitHub · GitHub
1 Like
Issue created with Workstation WG, can be found at Issue #426: Add openssl to the base system - fedora-workstation - Pagure.io
3 Likes
Of course, it could be done by adding the GSConnect extension package to the base image of the Atomic variants, since that pulls in Openssl, as noted in response to my issue raised at the WS WG issue page. In the interim, wouldn’t that be an option?
Not all heroes wear capes
I follow the thread opened by jakfrost, and what i understand is that gsconnect already bundled with openssl in workstation with rpm package (Overview - rpms/gnome-shell-extension-gsconnect - src.fedoraproject.org), so i think for they dont make much sense add it on base, although for Atomics, situation is different