Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: set minimum before triggering updating dialogue #114

Open
algo01 opened this issue Aug 7, 2018 · 9 comments
Open

Feature Request: set minimum before triggering updating dialogue #114

algo01 opened this issue Aug 7, 2018 · 9 comments

Comments

@algo01
Copy link

algo01 commented Aug 7, 2018

Hello, I'm using dnfdragora in Fedora 27. It works great and is very helpful.

I wanted to suggest a feature to set a minimum before triggering updating dialogue. For example, several times a week I am updating only one package at a time. I'd rather be able to only have to update if there are 30 packages and do it less often.

Other than that, thanks!

@algo01 algo01 changed the title Feature Request: set a lower minimum before triggering updating dialogue Feature Request: set minimum before triggering updating dialogue Aug 7, 2018
@blackcrack
Copy link

👍 good suggestion :)

@anaselli
Copy link
Collaborator

If I understood correctly you are asking for an alert that does not tell you if there are updates, but if there are at least a given number of them.
If so, i can hardly understand why you need such a feature, don't get me wrong, I just want to understand it... :)
I mean if you don't update ignoring the alert, you can do that later when you feel to do it. And if you don't want to have so many alert during the day just increase the check time into configuration file.

@algo01
Copy link
Author

algo01 commented Aug 11, 2018

Well, the idea is to have less popups that are distracting. Maybe a better idea is to schedule by day of week. So, for example, only update on Friday.

Configuring is a bit confusing. On the gui it allows one to set the delay by seconds. I just checked the config file and you can set by minute. Actually, this raises the question if I set update_interval to 60 * 24 * 7 = 10080 is this based on clock time or time on the computer.

As a side note, I can't get into the gui unless there are updates. I try to launch the application and get the following error: dnfdaemon client error occurred: g-io-error-quark...locked by another application.

@anaselli
Copy link
Collaborator

It should be by minutes, based on a starting point let's say when you switch on the PC.
dnfdragora options
Anyway a set of choices could be added and your idea to add a check by schedule like:
once a day at, once a week at could be added... i would avoid once a month just because some updates are important and in a month we could have a lot of them... but i'm open to discuss here...

@anaselli
Copy link
Collaborator

btw, to test your changes without using the settings dialog, parameters are available into ~/.config/dnfdragora.yaml but you need to start dnfdragora again.

@anaselli
Copy link
Collaborator

concerning:

As a side note, I can't get into the gui unless there are updates. I try to launch the application and get the following error: dnfdaemon client error occurred: g-io-error-quark...locked by another application.

I need to check if there are some falling cases yet, i mean if dnfdragora is looking for updates that is correct, you cannot run another dnfdragora instance, dnfdaemon access is not allowed. But if dnfdragora is dead for any reason... that is a bug...

@blackcrack
Copy link

blackcrack commented Aug 12, 2018

may would be good if there a time-check too, in direction of cron,

  • check all [__]min [up to 60] (for developers / packers) if there more as [XXXX] Packets
  • check all [__]hower [up to 24](for developers / packers) if there more as [XXXX] Packets
  • check all [__]Day [up to 30](for Normal/Users/Admins/Providers) if there more as [XXXX] Packets
  • check all [__]Month [up to 12](for Normal/Users/Admins/Providers) if there more as [XXXX] Packets
  • --auto --auto-update / automatic update

therewith it is also possible to be fully up to date for developers too :)

best regards
Blacky

@anaselli
Copy link
Collaborator

The distros ideas should be to promote updates and avoid security issues. So i don't think a per number of packages is a good idea.... as well as a check range greater than a week i believe.... @Conan-Kudo @besser82 ?

@blackcrack
Copy link

blackcrack commented Aug 12, 2018

therewith have i make a eable for any day or ^^some, in direction what and how the user want, in direction free will, and the user can configuring it.
I have add also a automatic

  • --auto --auto-update / automatic update

for supporting some auto update for users who want have this automatic
and the user/developer/Provider can determine what he want.. or he can overwatch at all via dnf update in console, like the user want, but he have then a possible to config it, if he want not overwatch it .. and have fully trust in the Distributor ..

Maybe a "Update Configurator" (dnfupdateconfig), something in this direction maybe ..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants