[valtam]

Fixed dir structure. Please pull first.

[ralphy]

Ok, give me a little bit and I will pull/edit/push what I have... This is major surgery here :P

I need to backup what I have first.

Note: The clock icon and column will vanish when I push what I have... We can't use that icon in the dialog. But there is a pretty nice polishing otherwise.

[valtam]

No problem. FYI when I start a new GH repo, this is usually my process:

- Think of a useful tool missing from the OS.
- Throw together some bash and zenity code that is far from complete.
- Let it stew in my mind and push little ideas as they come to me.
- Refine.

[ralphy]

Ok Jerry, I've pushed it to GH. I'm going to open a pull request but I'm not going to merge it. I'll leave that up to you so that you can test whether you like it or not.

Note: After merging my pull request /usr/share/liteupdatenotify/icons folder is not longer needed or used. Can be safely removed.

[ralphy]

I just tested the cronjob and the cron won't run when the time is due. It runs manually executed but not on schedule. It happens that we are not setting the correct permissions. I have a clear idea of how to fix it... will look into correcting this problem.

Also, for testing purposes is OK what we have there but it is really not a good idea at all to remove the user's cron file under /var/spool/cron/crontabs/  because we will be effectively deleting all cron jobs a user may have scheduled. We need to sed -i this file instead... will get a sample later as time allows

[valtam]

Note: After merging my pull request /usr/share/liteupdatenotify/icons folder is not longer needed or used. Can be safely removed.

I'm going to leave that in there for now. It's early days in this app and there is the chance that there will be some icon representation there in the future. Just undecided at this point on what will look best.

[valtam]

I just tested the cronjob and the cron won't run when the time is due. It runs manually executed but not on schedule. It happens that we are not setting the correct permissions. I have a clear idea of how to fix it... will look into correcting this problem.

Also, for testing purposes is OK what we have there but it is really not a good idea at all to remove the user's cron file under /var/spool/cron/crontabs/  because we will be effectively deleting all cron jobs a user may have scheduled. We need to sed -i this file instead... will get a sample later as time allows

Yes, this is by no means the final implementation. This app is very young. Whichever solution you come up with it, feel free to push without waiting for me to merge. It is in the 'experimental stage' for sure.

[ralphy]

Well, I'm about to push the first fully tested (by me) update that actually does what this application requires... we are not longer removing the file but properly editing it and setting up permissions so it runs as needed.

What's been polished:

- user is allow to execute the application without administrative credentials.
- ask for credentials when adding schedule fails (elevate)
- check whether cronjob file exists or not
- added Disable Updates notification option
- create cron job file if it doesn't exist and insert an initial cron job (disable by default)
- update cron job file if it already exists and insert an initial cron job
- set correct permissions on user's cronjob file whether newly created or not
- files are not longer deleted but sed'd instead.

[valtam]

Fabulous, looking forward to testing this Ralphy.

Sent from my Phone using Tapatalk

[ralphy]

Fabulous, looking forward to testing this Ralphy.

Sent from my Phone using Tapatalk

Well, I've found 2 bugs so far :P

1- Click "Set" without selecting a schedule <= something needs to be defined in the code for that scenario.
2- If the user adds or removes any cron job manually under his/her own account then our application breaks because I used the wrong line as reference to sed changes.  :-[  sucks to be me! lol