Add package for rmstylusbutton

[MoritzBoehme]

I am adding the package RMStylusButton.
It's a fork of the unmaintained RemarkableLamyEraser.

With the package, one can:

• switch to the eraser by holding down the button of the stylus
• double click to undo
• triple click to redo

The upstream project uses a custom script for managing the installation which I used as a basis for the package scripts.
Currently, one cannot pass flags, but I plan to add this as well. Maybe using an env file which has a variable FLAGS which is then loaded via the service file.

[Eeems]

Please update the package recipe to better match the standards we have for our recipes as a whole. I've added comments with change suggestions.

Please also add a conflicts with the remarkable-stylus package, as these both handle the same thing, and installing both at the same time can cause unexpected results.

[MoritzBoehme]

Please update the package recipe to better match the standards we have for our recipes as a whole. I've added comments with change suggestions.

Please also add a conflicts with the remarkable-stylus package, as these both handle the same thing, and installing both at the same time can cause unexpected results.

Thanks for the quick feedback! Will get right on it.

[MoritzBoehme]

I have added the conflicts as well as a basic way to configure the package if desired via /opt/etc/rmstylusbutton.env. I do not know how this works in combination with package updates, though. Any changes will probably get overridden?
I'll search how other packages do it...

[MoritzBoehme]

Well, it seems other packages do it similarly. Renamed the config file to end in .conf to make it clear that this is a config file.
Hope this complies with best practices and the style of this project.

[Eeems]

Generally for this kind of configuration, users would create a systemd unit override. Configuration files are generally something that the underlying application reads. I'm not sure it's really something we would desire as a separate file in this case

[MoritzBoehme]

Generally for this kind of configuration, users would create a systemd unit override. Configuration files are generally something that the underlying application reads. I'm not sure it's really something we would desire as a separate file in this case

Ah, okay. Thanks for clarifying. I'll read up on how this would work and change the package accordingly.

[Eeems]

Generally for this kind of configuration, users would create a systemd unit override. Configuration files are generally something that the underlying application reads. I'm not sure it's really something we would desire as a separate file in this case

Ah, okay. Thanks for clarifying. I'll read up on how this would work and change the package accordingly.

A user would run systemctl edit rmstylusbutton, Make their modifications to pass the flags, save and exit. This would create an override file that overrides the settings they want to override. This would persist on package upgrades. They can remove the override file if they want to revert back to stock settings.