| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
tiebreaking
|
| |
|
|
|
|
|
|
|
|
| |
By introducing a new package metadata field, `provider_priority`
(index letter `k`), we can specify default packages to satisfy a
virtual.
If a user wishes to select an alternative provider for the virtual,
a changeset swapping the default provider for the selected provider
will be generated by the dependency resolver.
|
| |
|
|
|
|
|
|
|
|
|
| |
this fixes package selection when a 'real' package exists, but would
need to be provided by another package with 'virtual provides'.
In current package database this can happen with postgresql which is
also provided by postgresql-bdr. Normally postgresql would be satisfied
by postgresql, but if any package depends on postgresql-bdr and there's
no versioned dependency on postgresql this will help apk figure out
that postgresql-bdr should be used.
|
| | |
|
| |
|
|
|
| |
Mistakenly allowed masked out package to be installed if it was
in cache.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
If name N is required, and all providers of A also provide B, it
means that only instances of B can be selected that provide N. This
is strong help with cases when so:libfoo.so.1 is updated to
so:libfoo.so.2 and not everything is recompiled.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Select latest version of package (if it is not pinned), and print
error if it cannot be installed due to other dependencies.
Together with --available, it selects the latest package which is
present at least in some repository.
This also fixes few solver issues with ordering of package selection
that got quite apparent with this flag. Namely, we cannot "lock"
a package until it's reverse dependencies are locked or not all of
the solver flags are propagated properly.
|
| |
|
|
| |
mostly useful for reboot, when all packages are not available.
|
| |
|
|
|
|
|
| |
- try harder to not change anything during self-upgrade
- also honor locking to packages that where earlier used in
merging common dependencies
- clarify upgrade applet help messages
|
| |
|
|
| |
Fix also pinning test cases to be more sane.
|
| |
|
|
|
| |
Handle properly per-name preference flags, and add test cases
for testing those via fix applet.
|
| |
|
|
|
| |
Implementing basic dependency handling, install_if and awareness
of pinning.
|
| |
|
|
| |
This reverts commit a2d873a77c6dd2e7f6219e6941af796e1f904e69.
|
| |
|
|
| |
This reverts commit 84bfef1a6b587a7da7d12fb701ab0d1d5d6ce2a9.
|
| |
|
|
|
| |
We are having so many packages that they might overflow otherwise.
"ERROR: Preference overflow" was already reported.
|
| |
|
|
|
|
| |
It is incorrect optimization causing valid solutions to be skipped.
Any performance it might've gained, should be fixed by reintroduction
of the minimum penalty logic added in previous commit.
|
| |
|
|
| |
Basic per-name per-package specific scoring added.
|
| |
|
|
|
|
| |
Enabled when all attempts to satisfy a name failed, we know that we
can ignore all decisions until we find a decision affecting the name
we wanted to satisfy.
|
|
|
apk_name_state is now quite small; and we avoid overhead of two
pointers (+ malloc overhead) when we just make it part of apk_name.
It also fixes some problems (that got introduced) where apk_name_state
was not allocated.
|
