redshift: patch for wayland, AppArmor

[CameronNemo]

I like to think there is a little something for everybody in here.

[maxice8]

With that it will work on all wayland wlroots compositors and ones that support the same protocol ?

[CameronNemo]

Yes indeed! See sharpbracket/redshift#704

[maxice8]

On Sat, Mar 16, 2019 at 01:46:37AM -0700, Cameron Nemo wrote: Yes indeed! See sharpbracket/redshift#704 -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #9909 (comment)

Nice

[Cogitri]

Why not wait for upstream to merge this?

Edit: Nvm, I guess this is for people who are interested in trying it now?

[CameronNemo]

@Cogitri yeah, not sure when upstream is going to merge and release, figured people may be interested considering that sway 1.0 is out.

[Cogitri]

Ah, alright

[ericonr]

Heh, thanks for the patch! Do you think we could talk to this guy https://github.com/minus7/redshift/tree/wayland about releasing a version in their repo? It'd be great to have that actually packaged.

[CameronNemo]

I have actually been thinking about forking. I have merged quite a few fixes into this branch https://github.com/CameronNemo/redshift/commits/master

[ericonr]

Are all of those fixes integrated into the current template?

[CameronNemo]

Not at all. Current template is unpatched.

[jnbr]

I'm against adding patches adding functionality.

I have actually been thinking about forking.

If upstream isn't accepting your patches or is not moving at all, please do so.
Adding large amount of patches into void-packages is not sustainable in the long term.

[ericonr]

@CameronNemo if you do fork it and have a definitive template for it, add /etc/apparmor.d/local/usr.bin.redshift as a conf_files.

[CameronNemo]

#23643