Page 1 of 1

Controlling Repository Updates

Posted: Thu Oct 07, 2021 12:20 am
by JASpup

Has anyone wondered:

Why does a ppm repository update revise all repositories instead of just the ones you have checked to appear in the main gui window?


Re: Controlling Repository Updates

Posted: Thu Oct 07, 2021 3:13 am
by bigpup

Basically because it is coded to update all repositories in the database of repositories.
After updating the database.
No matter which repository you choose to look in.
It will be as updated as the others.

Depending on the specific version of PPM.
It may stop at each repository and require you to make a decision to update or not.
But this feature was not liked by most people.
Having to answer this question 6, 8, 10 or more times, before the update process completed.

There are more problems, using PPM with a old outdated repositories database, than using an, always updated one, before downloading something.


Re: Controlling Repository Updates

Posted: Thu Oct 07, 2021 3:40 am
by JASpup

Auto-updating at once is more convenient.

You have to read little print to see if it's worth skipping one.

At the same time, you're forfeiting the right to be selective.

Maybe it would save time and bandwidth if there were a judicious way of choosing?

Unless there's a technical reason to update everything, for me it's an issue of a feature working as expected.