PR#8: Enhance greenfield installation usability with newly recommended driver set - rpms/sway

rpms / sway

#8 Enhance greenfield installation usability with newly recommended driver set

Merged 3 years ago by thofmann. Opened 3 years ago by jpokorny.

rpms/ jpokorny/sway greenfield-installation-usability into master

Enhance greenfield usability readiness...

Jan Pokorný • 3 years ago

b7846de

sway.spec

file modified

+9 -1

		`@@ -1,6 +1,6 @@`
		`Name: sway`
		`Version: 1.4`
		`- Release: 6%{?dist}`
		`+ Release: 7%{?dist}`
		`Summary: i3-compatible window manager for Wayland`
		`License: MIT`
		`URL: https://github.com/swaywm/sway`
		`@@ -39,11 +39,16 @@`
		`BuildRequires: scdoc`
		`# Dmenu is the default launcher in sway`
		`Recommends: dmenu`
		`+ # In addition, xargs is recommended for use in such a launcher arrangement`
		`+ Recommends: findutils`
defolos commented 3 years ago Shouldn't this be pulled in by dmenu instead?

		`Requires: swaybg`
		`# By default the Fedora background is used`
		`Recommends: desktop-backgrounds-compat`

		`+ # Lack of graphical drivers may hurt the common use case`
		`+ Recommends: mesa-dri-drivers`
		`+`
		`# dmenu (as well as rxvt any many others) requires XWayland on Sway`
		`Requires: xorg-x11-server-Xwayland`
		`# Sway binds the terminal shortcut to one specific terminal. In our case urxvtc-ml`
		`@@ -96,6 +101,9 @@`
		`%{_datadir}/backgrounds/sway`

		`%changelog`
		`+ * Sat May 30 2020 Jan Pokorný <jpokorny@fedoraproject.org> 1.4-7`
		`+ - Enhance greenfield readiness with optional pull of default driver set & xargs`
		`+`
		`* Thu Apr 30 2020 Aleksei Bavshin <alebastr89@gmail.com> - 1.4-6`
		`- Add patch for layer-shell popups layer (#1829130)`

jpokorny commented 3 years ago

Based on my recent experience.

I think that people using drivers not packaged in Fedora can
resolve the situation easily with disabling recommended packages
as such; they are on their own in multiple ways already, so taking
care of installing any other recommended packages is relatively
small overhead compared to the full burden (or alternatively,
having some drivers around they won't use -- I think it is physically
infeasible to have a single machine full of accelerators such that
every single one in mesa-dri-drivers is used, anyway, so all
users already have drivers on their systems they won't use)

And those still with Xorg for sway (if still possible) ... striking?

rebased onto 1f89b84

3 years ago

jpokorny commented 3 years ago

Realized that xargs (as in default config) was also only implicitly
assumed, better not to rely on that.

rebased onto b7846de

3 years ago

defolos commented on line 14 of sway.spec 3 years ago

Shouldn't this be pulled in by dmenu instead?

jpokorny commented 3 years ago

@defolos xargs is referred to in /etc/sway/config which is used by default.

And I extrapolate it is recommended regardless what menu runner you use
these days in your custom configuration.

If it's used by dmenu, it should just copy this requirement, since the
dependencies would be independent.

Edited 3 years ago by jpokorny

defolos commented 3 years ago

Well, imho xargs shouldn't get added here, but I'd leave the decision to @thofmann.

jpokorny commented 3 years ago

That's not a matter of someone's taste, and no actual counter-arguments
were raised. It's not a constructive approach. Also, if you don't have it in
your config, you are giving up on the feature justifying the use of xargs
as arranged in an upstream example config that's derived in Fedora.

I hope you do realize that without findutils, menu and hence whole
experience in pristine state is "unusable desktop".

Is some 1766 KiB an overkill that cannot be sacrificed in minimalistic
deployments? Most of that is because of the localization -- that's where I'd
look if you are obsessed with bit creep, also perhaps in the context of
minimization initiative.
EDIT: topic already opened.

Note, I go minimalistic on my own, and suffered way too much recently[*],
simply because maintainers do not realize the distinction between
"works for me" and "works universally" :-/
Not sure if sway should impose such troubles on new comers, especially
those with greenfield/fresh installs?

[*] wasn't the case with sway, I happened to notice early when comparing
my old configs.

Edited 3 years ago by jpokorny