should __package update index by default? #68
Labels
No Label
bugfix
cleanup
discussion
documentation
doing
done
feature
improvement
packaging
Stale
testing
TODO
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ungleich-public/cdist#68
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
too often I got errors about package not found because index is old or not existent. to avoid that, i added
__package_update_index
(with reasonable maxage) which is required for__package
's. but that's not perfect for obvious reasons.__package
is non-parallel, so first instance of__package
also updates index. but that type is just a wrapper, which has no knowledge of state of package and we don't want to update index if no package install is going to happen.this logic should be implemented separately for every package type. for example,
__package_apt
will call__package_update_index --type apt --maxage ?
in type manifest, if installation will happen. or maybe we should refactor index update logic into own types eg__package_apt_update_index
?also, what should be reasonable maxage?
PS,
__apt_update_index
should be depreacted 😄PS2, happy holidays 🎅
closed
this issue is resolved for me.
mentioned in merge request !842
changed the description
changed the description
changed title from should __package update {-package -}index by default? to should __package update index by default?