FS#63286 - [wlroots] Add rootston when packaging

Attached to Project: Community Packages
Opened by Omar Pakker (Omar007) - Friday, 26 July 2019, 21:56 GMT
Last edited by Brett Cornwall (ainola) - Tuesday, 30 July 2019, 01:12 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Brett Cornwall (ainola)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The wlroots package in community does not currently include rootston in package().
It is build as part of the wlroots build process but not installed by `ninja install` thus not included in the final package at the moment.

Please add it as a part of wlroots (or maybe make it a split package? I have attached the patch I currently apply to this package locally).
The files in question are:
- build/rootston/rootston (binary)
- wlroots-0.6.0/rootston/rootston.ini.example (example config file)
   split-pkg.patch (1.5 KiB)
This task depends upon

Closed by  Brett Cornwall (ainola)
Tuesday, 30 July 2019, 01:12 GMT
Reason for closing:  Implemented
Additional comments about closing:  Thanks, I've merged parts of your patch. I did not enable RDP due to https://bugs.archlinux.org/task/62809?pr oject=5&dev=20134. The config file was also installed to /usr/share/doc/wlroots instead of /usr/share/doc/rootston, and rootston was missing a file.

I've pushed a new version; you should receive this update shortly.

Thanks for the report!
Comment by Brett Cornwall (ainola) - Sunday, 28 July 2019, 16:52 GMT
Thanks for the report, Omar.

I'm not sure what the use-case for rootson would be in [community]. As it is a reference compositor I feel its value would be very limited compared to potential maintenance burdens. My initial reaction is that rootston would best be served in the AUR.
Comment by Omar Pakker (Omar007) - Monday, 29 July 2019, 00:08 GMT
I'd say the use-case is the same as for weston. I can see where you're coming from though.

From what I can tell, the potential maintenance burden (as it stands now) is actually greater if it's somewhere as a completely separate package (be it AUR or a non-split package somewhere else).
Afaik, the build for rootston is completely tied/depending on the build of wlroots and you can't build one without the other.

I.o.w. if anything changes for the wlroots package in Arch and it's separated to that extreme, there's a big chance problems arrise due to wlroots <-> rootston build mismatches. I guess that could be fixed by constraining rootston to the exact package+PKGBUILD version of the wlroots package in [community] it was based on, but that just creates update conflicts every single time if separate people are maintaining separate parts of the same upstream project.

Loading...