rMscreens #571
rMscreens #571
Conversation
|
I would really recommend adding help output to the script. I don't think we can merge this until pr0fsmith/rMscreens#2 is resolved though. |
|
@pr0fsmith did you have a chance to address the requested changes? |
I will do that today. |
|
@Eeems All changes have been made. |
|
@pr0fsmith I don't see any changes to this PR? Did you intend to update the source and sha256sum in the package file to pull in the latest changes? |
@Eeems I actually didn't make any changes. It seems as though I made the changes months ago so the existing source should be fine. |
|
@pr0fsmith it looks like this is still pointing at an old commit and doesn't have the changes that were requested. |
|
@pr0fsmith poke |
|
I want to but I honestly dont understand how. I find the whole process confusing.
Sept 26, 2022 10:57:48 a.m. Nathaniel van Diepen ***@***.***>:
… @pr0fsmith[https://github.com/pr0fsmith] poke
—
Reply to this email directly, view it on GitHub[#571 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AM5FBGDMLBTMCII7ERDT6STWAG2WZANCNFSM5QXGBEYA].
You are receiving this because you were mentioned.[Tracking image][https://github.com/notifications/beacon/AM5FBGE4MJ4U3C4D37BGVELWAG2WZA5CNFSM5QXGBEYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOJL7BYWY.gif]
|
|
@pr0fsmith I've added a comment showing what needs to be changed. There is a button to directly apply the suggested changes. Updates to your repository don't automatically show up here as we point at specific commits so that we know that the source doesn't change between builds. Whenever you update your repository you need to point the recipie at the new commit. |
Co-authored-by: Nathaniel van Diepen <Eeems@users.noreply.github.com>
|
I don't understand how to change the recipe. You did it for me last time. |
If you go to the files changed tab, you'll see the recipie there. It's the |
|
@pr0fsmith I can't get this to work, there is no help output. When looking at the comment in the script saying how to use it, that doesn't work. It looks like your argument parsing has a loop where it will never work as both -c and -n expect the other setting to already be set. |
|
@pr0fsmith any chance you could get this cleaned up and ready? I'd love to get it merged. |
|
It would be nice to have this automatically do a backup/restore on install, but we'd need a better mechanism to make sure that normal usage can't interfere with what files are backed up or restored. |
* Add changescrn package --------- Co-authored-by: Nathaniel van Diepen <Eeems@users.noreply.github.com>
### New Packages - `reterm` - 0230628.1927-1 (#703) - `sill` - 0.1.1-alpha (#719) - `changescrn` - 1.0.0-1 (#571) ### Updated Packages - `yaft` - 0.0.8-2 (#715 #716) - Update to 0.0.8 - Depend on `terminfo` - Add patch to start bash as a login shell - `toltec-base` - 1.2-2 (#715) - Adds `/opt/etc/profile` to `/etc/profile.d` so that it automatically loads the environment variables provided by the entware source - `linux-mainline` - 6.2.0-1 (#657) ### Tooling - Update build process to use Python 3.10 (#684) - Added issue templates to the repository (#711)
rMscreens is a commandline utility that allows you to easily change your rM screen (sleep screen, power off screen etc). It can also be used to backup and restore your original screens easily.
I wrote this code myself and tested it on the rM2 software version 2.12 https://github.com/pr0fsmith/rMscreens/blob/main/changescrn