move to use v5.36;
tested by me over the last few weeks, and tb@
also fixed a "manual install" bug properly reported by tb@

aside that there should be *no functional change*.
If you see any message

move to use v5.36;
tested by me over the last few weeks, and tb@
also fixed a "manual install" bug properly reported by tb@

aside that there should be *no functional change*.
If you see any message like "hey, the number of params is wrong"
it is a fringe case I didn't run into and should be easy to fix.

show more ...

somehow, I thought I was recording destdir there, but I'm not.

avoid some warning message, normal dirs don't have any log info registered

don't store full directory objects if they're not "special", just knowing
there's a directory that should stay around is enough.
shaves on the number of shared directories for shared items quite a lo

don't store full directory objects if they're not "special", just knowing
there's a directory that should stay around is enough.
shaves on the number of shared directories for shared items quite a lot.

show more ...

handle failures from ports tree with more care.
this does avoid infinite loops in case of wrong plists.
necessary since print-plist-with-depends CAN fail...

initial scaffolding for @rcscript: for now, acts like normal files,
but allow absolute pathnames (treat that as an implicit @cwd).

sort journal messsages in a better way, put - before +, so that one can
see deinstall info before new install info (prompted by a comment from
tedu@)

fix the qt 4.5 -> 4.6 update issue.
since we usually deal with directories in a global way, replacing a
directory with something else didn't work.
the fix is to record removed directories in Vstat in

fix the qt 4.5 -> 4.6 update issue.
since we usually deal with directories in a global way, replacing a
directory with something else didn't work.
the fix is to record removed directories in Vstat in a "lazy" way:
we only test these objects for existence if we add something else at
the same location. Since this happens rarely, we can afford to perform
the whole SharedItems dance twice...

show more ...

allow say and errsay to work without parameters, as it's ways common.
create verbose_system up in state, because it makes sense without verbose.

whitespace cleanup

reuse for_list

ui changes: go thru a state object for most printouts

whitespace fixes

make the final progress bar vanish unless verbose >= 2, as requested by
Theo.

consistent spelling

much simpler SIG{INFO} handling: create a status object in state and
update it when needed. Install a SIG{INFO} handler at start that will do
what's needed.

change verbosity handling: be silent by default, turn on the first level if -v.
Add more levels, specifically, lots of info regarding individual files only
visible if -vvvvv.
Make -n display the same

change verbosity handling: be silent by default, turn on the first level if -v.
Add more levels, specifically, lots of info regarding individual files only
visible if -vvvvv.
Make -n display the same stuff as normal (need -n -v to display more stuff).
Introduce -s, "size-only", turns on -n and does skip any extraction.
Sprinkle handlers for SIG_INFO, not really nice yet.

Note that -n is non functional for complex updates, because of caching
issues I have to fix.

show more ...

be slightly more paranoid about shell stuff we run.

vsystem, system, unlink can mostly go through state, and do the ->clear part
as well.

remove forwarders, and provide a sensible API that says what's going on
(e.g., we're logging information for later).

bad espie: use strict/warnings consistently, and fix two nits and two
actual errors !

sprinkle code to deal gracefully with absent packing-lists.
makes it easier for people to recover after a disk crash that
leaves /var/db/pkg half-empty.

use OpenBSD::Paths contents

refactor ProgressMeter code to create objects, put these into state.
Create a common state class for delete and add, put the progressmeter
creation in there.

neat effect: we don't have a progressmet

refactor ProgressMeter code to create objects, put these into state.
Create a common state class for delete and add, put the progressmeter
creation in there.

neat effect: we don't have a progressmeter, we use a stub class instead
and *never* pull the code in at all.

show more ...

introduce a SharedItemsRecorder (put it into Vstat, since that's a file
common to Add and Delete, for now).

Use it to have common code that records items to remove / items remaining.

Stash it into

introduce a SharedItemsRecorder (put it into Vstat, since that's a file
common to Add and Delete, for now).

Use it to have common code that records items to remove / items remaining.

Stash it into pkg_add/pkg_delete state, and abstract the cleaning up
operation into the SharedItemsRecorder (so that pkg_add and pkg_delete no
longer have to know about the internals of SharedItems at all).

show more ...