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 ...

try/catch to be revisited

stop using old-style prototypes except where strictly necessary
(for try/catch)

signatures will be much more powerful once I move to 5.36

GC old catchall
add a better framework for signal handling (not used yet)

explain some details

separate the atend behavior, because dpb wants a pure signal intercept
but not an END code.

This fixes the stupid bug I had. Was looking in the wrong location,
not surprisingly

tweak register a bit... END {} code is obviously the problem

gc old functions, that part is clean as well...
so it's obviously the END code then...

backout previous commits for now; some of this is shared with dpb and
results in problems. hints from pvk@ about what introduced the breakage
we were seeing, who confirms that this backout fixes thin

backout previous commits for now; some of this is shared with dpb and
results in problems. hints from pvk@ about what introduced the breakage
we were seeing, who confirms that this backout fixes things; comitting
early to unbreak package builds.

====
a bunch of changes, all related to error-handling:
- have Handle->register also create a proper END block, so that
individual packages don't have to, and explain the issue
- kill old Unlink/Copy code that migrated to State years ago
- commonalize try{} catch {} for pkg_add/delete and pkg_create, so that
debug works the same way in both.
- switch printing command name to the catch handler, so that exceptions
are simpler to handle

and a few comments for the hairy parts...

Members:
OpenBSD/AddCreateDelete.pm:1.44->1.45
OpenBSD/AddDelete.pm:1.87->1.88
OpenBSD/Error.pm:1.33->1.34
OpenBSD/PackageRepository.pm:1.164->1.165
OpenBSD/PkgCreate.pm:1.160->1.161
OpenBSD/State.pm:1.58->1.59
OpenBSD/Temp.pm:1.34->1.35
====

show more ...

a bunch of changes, all related to error-handling:
- have Handle->register also create a proper END block, so that
individual packages don't have to, and explain the issue
- kill old Unlink/Copy code

a bunch of changes, all related to error-handling:
- have Handle->register also create a proper END block, so that
individual packages don't have to, and explain the issue
- kill old Unlink/Copy code that migrated to State years ago
- commonalize try{} catch {} for pkg_add/delete and pkg_create, so that
debug works the same way in both.
- switch printing command name to the catch handler, so that exceptions
are simpler to handle

and a few comments for the hairy parts...

show more ...

tweak the way we report bugs
- the catch/catchall distinction is no longer relevant, strip some info
by default now
- use state->{cmd} to display the command name properly

This makes sure final disp

tweak the way we report bugs
- the catch/catchall distinction is no longer relevant, strip some info
by default now
- use state->{cmd} to display the command name properly

This makes sure final displays show the command name.

show more ...

recent perl have signal names we don't have, protect against that.
also, allow child_error to take a parameter so that this can be used to decode
an arbitrary wait() result.

File::Path::rmtree is very stupid and spews out warning messages if there's
no cwd.

Well, if there's no cwd, we don't care about getting back there, so wrap
rmtree to just move to / before calling t

File::Path::rmtree is very stupid and spews out warning messages if there's
no cwd.

Well, if there's no cwd, we don't care about getting back there, so wrap
rmtree to just move to / before calling the real rmtree.

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).

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

more printing changes.

move log operations into their own file, since they're used outside of
pkg_add/pkg_delete by pkg_check.

move all system stuff to State, so that printing can be localized/cont

more printing changes.

move log operations into their own file, since they're used outside of
pkg_add/pkg_delete by pkg_check.

move all system stuff to State, so that printing can be localized/controlled.
Create primitives _print, _errprint, _fatal for overriding output, without
localization.

Accordingly, move a lot of code out of Error. We should also move Unlink and
Copy eventually.

show more ...

whitespace fixes

simplify using //=

simplify caching: return $cached->{$_} //= new_value;
remove stats
cache LibSpec as well (1000 c.53.0 !)

use Carp directly, it it very inexpensive actually, since it's been rewritten
to be just a very small stub that loads Carp::Heavy on demand.
Also, stop wrapping messages in "Expected", doesn't give u

use Carp directly, it it very inexpensive actually, since it's been rewritten
to be just a very small stub that loads Carp::Heavy on demand.
Also, stop wrapping messages in "Expected", doesn't give us anything.
Finally, make RequiredBy calls be carp, so that we actually know where they
fail...

show more ...

move signal catching up, so we can clean repos and temp files at once.
Fix main program try/catch: signal message should use standard form so
it gets caught.

common pattern, put it there since everything uses Error.

make these independent from Getopt, require Exporter