History log of /openbsd/usr.sbin/pkg_add/OpenBSD/PackageInfo.pm (Results 1 – 25 of 65)
Revision Date Author Comments
# 039cbdaa 13-Jun-2023 espie <espie@openbsd.org>

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


# 07126a4d 17-May-2023 espie <espie@openbsd.org>

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

signatures will be much more powerful once I move to 5.36


# 4eb7f0e4 15-Feb-2022 espie <espie@openbsd.org>

simplify code based on afresh1@'s remark: indeed I always need to
have a state once I'm past the initial locking


# d19342eb 14-Feb-2022 espie <espie@openbsd.org>

make db locking self-contained


# 47df9083 28-Jan-2020 espie <espie@openbsd.org>

match opendir with closedir... not that important as the thing was most
probably GC'd.


# afe6de13 11-Jan-2014 espie <espie@openbsd.org>

a bit of spring cleanup in advance: scrape old stuff that's not really
used.


# 45019a4a 09-Jan-2014 espie <espie@openbsd.org>

bump copyright to 2014


# 640de819 07-Jan-2014 espie <espie@openbsd.org>

scrape support for old +COMMENT file.
8 years of backward compatibility is long enough... :)


# bf7b7265 07-Jan-2014 espie <espie@openbsd.org>

recognize special file +META


# 67515dec 23-Aug-2011 espie <espie@openbsd.org>

zap old INSTALL/DEINSTALL stuff, it's been deprecated for 3 years, and removed
from pkg_create for over a year.


# 8f4d7b1a 18-Aug-2011 espie <espie@openbsd.org>

tweak


# 681090d4 12-Jul-2011 espie <espie@openbsd.org>

new pkg_delete, very similar to pkg_add, support for -a


# 8d5333ba 29-Dec-2010 espie <espie@openbsd.org>

more stuff that uses print directly dies


# 85d1f632 24-Dec-2010 espie <espie@openbsd.org>

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


# 000ce162 27-Oct-2010 espie <espie@openbsd.org>

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


# b0dfb814 30-Jun-2010 espie <espie@openbsd.org>

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.


# a3f853c2 30-Jun-2010 espie <espie@openbsd.org>

whitespace cleanup


# bc7bdd12 30-Jun-2010 espie <espie@openbsd.org>

simple use of new state->repo API


# 7e83eca3 09-Jun-2010 espie <espie@openbsd.org>

ui changes: go thru a state object for most printouts


# a409537d 04-Jun-2010 espie <espie@openbsd.org>

move code around, so that commands can be used as modules.
pkg becomes the start hub, which does nothing except require the
correct module.
Saner code wrt Add/Delete, and more sharing.


# d57bb46a 10-May-2010 espie <espie@openbsd.org>

whitespace fixes


# cba4982d 15-Nov-2009 espie <espie@openbsd.org>

make these independent from Getopt, require Exporter


# 662ab648 11-Nov-2009 espie <espie@openbsd.org>

progressmeter puts STDOUT in autoflush if -t, so that it can display to it instead of piping a lot of stuff to STDERR.

Go through state->print for most messages, so they will NOT do weird things
wit

progressmeter puts STDOUT in autoflush if -t, so that it can display to it instead of piping a lot of stuff to STDERR.

Go through state->print for most messages, so they will NOT do weird things
with the progressmeter.
Use a ->say shortcut which does the same thing that perl 5.10 say does...

show more ...


# ced26bd5 11-Nov-2009 espie <espie@openbsd.org>

state->progress->print => $state->print


# 0fbefedd 10-Nov-2009 espie <espie@openbsd.org>

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


123