| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
Instead of having a null pointer, use a dummy array which just
says the array is empty. This helps in multiple places of the code
which would otherwise need explicitly need to check first if the
array exists. This has been cause of multiple seg.faults in the
past as the array check is easily omitted.
This also removes (or fixes) all existing checks accordingly.
|
|
|
|
especially important if the package requested from command line
does not exist. otherwise we would not print an error at all.
|
|
Print more information why installation changeset calculation failed.
Fixes #187.
|
|
To print upgrading if package is actually being changed instead of
pure reinstall.
|
|
If version is equal, but package contents are different we should
show the package being upgraded.
|
|
In addition to autocleaning dependencies on deletion, we need to
autoclean the old package on upgrade too. This is to make sure that
obsoleted dependencies (existed previously, but not in new package)
are removed where appropriate.
|
|
they do not have any package associated. this is indicated by
package with zero installed_size.
|
|
even if we have only one package as candidate, we need to check
it's availability. otherwise we can endup with bad changeset
referring to unavailable package.
|
|
prints like:
(1/12) Installing...
(2/12) Installing...
etc...
|
|
This makes things a little bit nicer when installing from network with
slow lines.
|
|
When pressing only <enter> on the question "..continue [Y/n]?" then
lets take that as a "yes"
|
|
otherwise we would not be able to pick a package that exists
as a candidate for re-installation. fixes #138.
|
|
- make virtual packages work again
- make apk del (for non-empty packages) work again
|
|
allow also overriding old (possibly bad) world dependency.
hopefully it's more bullet proof now.
|
|
|
|
this makes the database package entry smaller, and we propbably
get more fields to installed_package later too. this cleans up
the way scripts are stored and is a preparation for supporting
triggers. some parsing for trigger meta-data. ref #45.
|
|
so do not skip it even if it's no longer available.
|
|
|
|
instead enforce world dependencies when the package name
is first referenced upon.
|
|
this helps boots sequence when network is not available.
|
|
|
|
|
|
|
|
so do not choke on it.
|
|
also makes it possibly to upgrade package without adding it to
top-level deps. fixes #69.
|
|
previously they might have been skipped on certain situations.
this also fixes some other reverse dependency enforcements and
implements new "pending" state for locked name.
|
|
and by default just update the world, and dump a lost of packages
that are not removed. fixes #47.
|
|
this way we never change cwd, and relative filenames are always
parsed consistently. this also helps filename construction in many
places. this patch also changes '--root' to override location of
all configuration to be in the new root. previously it depended
on the file which one was used.
|
|
and use that to figure if questions are allowed or not instead
of the verbosity level.
|
|
|
|
we might have done already something.
|
|
That will make the upgrade prefer packages available in repositories.
This is good if one want's to downgrade packages by removing an experimental
repository. Or to force re-install of locally built vs. repository version
when the package version are same, but checksum is different. Fixes #51.
|
|
make apk_version_compare() take strings rather than blobs
add apk_pkgversion_compare(), a wrapper that takes packages
|
|
|
|
|
|
|
|
|
|
Automatically remove packages that are no longer required by a top
level dependency.
|
|
Refuse to delete explicitly specified top-level packages unless
--force is specified.
|
|
Enforce name_id to be within apk_state allocated area. New apk_name:s
can be created later for e.g. unknown packages requested at command line.
|
|
|
|
|
|
|
|
Fixes #24.
|
|
Calculate changesets directly by stabilizating the package graph instead of
recalculating the whole graph and then diffing (similar approach as seen
in 'smart' package manager). The algorithm is not complete: defferred
search space forking is missing. So you don't always get a solution on
complex graphs.
Benefits:
- usually the search state tree is smaller (less memory used)
- speed relational to changeset size, not database size (usually faster)
- touch only packages related to users request (can work on partitially
broken state; upgrades only necessary packages, fixes #7)
Also implemented:
- command prompt to confirm operation if packages are deleted or downgraded
- requesting deletion of package suggests removal of all packages depending
on the package being removed (you'll get list of packages that also get
removed if you want package X removed)
- option --simulate to see what would have been done (mainly for testing)
- an untested implementation of versioned dependencies and conflicts
A lot has changed, so expect new bugs too.
|
|
|
|
|
