track firmware separately, since those will appear as uptodate for us

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

yeah, yeah, those names are horrible

spelling fixes; from paul tagliamonte
any parts of his diff not taken are noted on tech

partial backout of 1.166: we still need to compute the pkgname without the
repo for debug packages, but we need the full path for the handle (for now)

fixes regression noticed by bluhm@

close the gap for the "final" hint that did not install debug packages
(coincidentally, that's the pattern used for install from ports)

This just requires always passing pkgname thru parse to extrac

close the gap for the "final" hint that did not install debug packages
(coincidentally, that's the pattern used for install from ports)

This just requires always passing pkgname thru parse to extract the right
name.

There's definitely a bit of code to clean up in pkg_add afterwards :/

show more ...

preliminary addition of -d option (semantics: add debug packages if
they're present along the packages we want to add/update)
probably not perfect yet, but 100% a no-op if it's not used, so won't
bre

preliminary addition of -d option (semantics: add debug packages if
they're present along the packages we want to add/update)
probably not perfect yet, but 100% a no-op if it's not used, so won't
break existing usage.

show more ...

better signatures.
- pass state along to be able to do proper errsay instead of raw printing.
- compare VERSION markers first, because they're supposed to trump
everything else.

(todo: evaluate -v d

better signatures.
- pass state along to be able to do proper errsay instead of raw printing.
- compare VERSION markers first, because they're supposed to trump
everything else.

(todo: evaluate -v diagnostics for version bumps)

okay sthen@

show more ...

document that some error should happen

tweak the ntogo messages slightly so that they work better in all situations

simplify how "kept" packages are handled. First, we never need their
full plist, just their update_info. Also, the routine for move_kept is
pretty much always the same, so fold it.

Finally, delay fu

simplify how "kept" packages are handled. First, we never need their
full plist, just their update_info. Also, the routine for move_kept is
pretty much always the same, so fold it.

Finally, delay full plists in create_old.

show more ...

no need to test for plist, we get the conflict_list since we have update_info

subject -z hints (fuzzy update) to quirks' tweak_search.
Reminded by sthen@
This solves the 5.4 -> 5.5 delete/reinstall gap for changed pkgnames.

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

bump copyright to 2014

have -DFW_UPDATE set @option firmware on downloaded firmwares.
- normal pkg_add -u should ignore them
- pkg_delete will ask about deleting them

okay landry@

fix autoloading of quirks: don't try to run quirks while processing the
quirks set, as we may accidentally load the old one.
also, in case we can't load quirks, report if quirks should be there,
e.g.

fix autoloading of quirks: don't try to run quirks while processing the
quirks set, as we may accidentally load the old one.
also, in case we can't load quirks, report if quirks should be there,
e.g., compilation error, without regard to verbose status

show more ...

a bit more scaffolding for running quirks. In particular, once quirks
have been loaded, complain loudly if something doesn't work.
(and complain when quirks don't load in !verbose mode)

In update verbose mode, when skipping an update candidate due to an
unmatching pkgpath, if no valid update candidates are found, print that
we are skipping the update candidate and all pkgpaths for b

In update verbose mode, when skipping an update candidate due to an
unmatching pkgpath, if no valid update candidates are found, print that
we are skipping the update candidate and all pkgpaths for both the
currently installed package and the skipped update candidate.

This is designed to help diagnosing issues when ports move locations
in the tree, but the necessary @pkgpath entries are not correctly added
to the PLIST.

Much help and OK espie@

show more ...

cleaner code: only wrap the call to quirks itself inside an eval.
anything else that could fail shouldn't be inside the eval.
create an object instead of saying "hey we're cool, let's let other
stuff

cleaner code: only wrap the call to quirks itself inside an eval.
anything else that could fail shouldn't be inside the eval.
create an object instead of saying "hey we're cool, let's let other
stuff break horribly".

show more ...

don't abort if that info is not yet available...

zap fatpackages. nobody actually uses them.
accordingly, locations do not need to track architecture.

tag fuzzy stuff for manual-installs too

another missing message

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