Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#62805 - [sway] Should sway now depend on swaybg?

Attached to Project: Community Packages
Opened by Nick (yonson) - Tuesday, 04 June 2019, 03:04 GMT
Last edited by Alexander F. Rødseth (xyproto) - Friday, 07 June 2019, 14:26 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Alexander F. Rødseth (xyproto)
Jerome Leclanche (Adys)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Description: Should sway now depend on swaybg?

Additional info:
* package version(s)
1.1
* config and/or log files etc.
* link to upstream bug report, if any
Release notes in 1.1 mention that swaybg is now a separate project, but should be depended on:
https://github.com/swaywm/sway/releases/tag/1.1

Steps to reproduce:
Install sway 1.1, try to use bg
This task depends upon

Closed by  Alexander F. Rødseth (xyproto)
Friday, 07 June 2019, 14:26 GMT
Reason for closing:  Fixed
Comment by Antonin Décimo (Rucikir) - Tuesday, 04 June 2019, 13:34 GMT
If swaybg is not installed, apparently sway shows a grey monochrome as background.
Could you consider adding swaybg, swayidle, swaylock as optional dependencies? Perhaps also waybar?
Comment by Carlo Abelli (carloabelli) - Tuesday, 04 June 2019, 14:35 GMT
From the release notes for sway 1.1:

> swaybg is now distributed as a standalone program which is compatible with many Wayland compositors. Unlike the other sway clients which have been split into separate projects, however, swaybg is a required dependency of sway. Packagers are encouraged to configure it as such when updating sway for their distribution.

So it seems like swaybg should be added as a dependency but swayidle, swaylock, etc. should not.
Comment by Antonin Décimo (Rucikir) - Tuesday, 04 June 2019, 15:59 GMT
> but swayidle, swaylock, etc. should not

I was suggesting *optional* dependencies, which makes more sense to me than dmenu, i3bar, or urxvt-unicode since they're directly related to sway.
Comment by Mayeul C. (MayeulC) - Wednesday, 05 June 2019, 06:38 GMT
I agree with OP on the second point as well, it would make discovery easier if those were listed as optional packages. Maybe also add slurp, grim and waybar to that list :)

Edit: and mako.
Comment by Alexander F. Rødseth (xyproto) - Friday, 07 June 2019, 14:26 GMT
Thanks for reporting! The updated sway package will appear in [community] shortly.

Loading...