Age | Commit message (Collapse) | Author |
|
|
|
|
|
point for people looking for packing-list details.
small tweak by tb@ for readability
okay tb@, jca@
|
|
|
|
|
|
|
|
do it
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
OK espie@
|
|
Recognize + only right before =
|
|
'+' is a widely used character in LIBxxx_VERSION, e.g. LIBFLAC++_VERSION.
Making it illegal breaks numerous packages.
|
|
|
|
|
|
|
|
to be used with REGRESSION_TESTING, where it's somewhat inconvenient to
know the full list in advance.
|
|
|
|
Extend it slightly: do not stub quirks, so that caching mechanisms work
as usual even when using stubs.
|
|
|
|
|
|
|
|
|
|
happens regardless.
Add a third one to only disregard base libraries
|
|
allows me to redefine methods to not do a thing
(maybe this will migrate to its own file if it grows enough)
|
|
|
|
|
|
and just say that instead of a dauntingly long list of packages
|
|
|
|
|
|
|
|
|
|
|
|
fullpkgname, as seen by Matthias Schmidt
|
|
|
|
|
|
"straightforward" is a better description at this point.
|
|
|
|
|
|
|
|
details of rc code to be set in stone later (currently as an option)
|
|
|
|
add a hook to compute the exit_code in more fun ways
|
|
"@option explicit-update" flavor of firmware circa 2013.
pkg_add hasn't needed to know about this since basically forever
|
|
don't pass parameters we don't need
|
|
also better method name
|