| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
reword the introduction to the stuff originally from FreeBSD to clarify
slightly.
|
|
idiom works.
|
|
than the length of the playfield, fill up the difference with whitespace.
Prevents leftover characters from previous message()s.
ok espie@
|
|
idea from deraadt@
|
|
* move the signature code to a packing-list method, prepend the pkgname.
* depend on distant listings, cache these systematically.
* cut the PKG_PATH at :/ systematically, much simpler than parsing URLs.
People should get used to trailing /s.
* let pkg_add -u actually run the update.
* check for signature in more places, for instance, let pkg_add installed_stuff
be a void operation.
* grab enough stuff during updates to check signatures, so that pkg_add -u
can report updates that are not needed right away, instead of waiting
for the more confusing `trying to update'
* beginning of @module support.
* @pkgpath support, including updates.
* systematically expand stems when applicable.
* use visitors systematically in pkg_info.
* pkg_info -S reports signature.
* remove hardcoding of categories in PackingList, so that future modules
will be able to expand them.
* add @updateset and @incompatibility keywords.
|
|
and this gives a hint about what is going on for big packages (like tetex).
|
|
fixes an elusive problem reported ages ago by sturm@...
|
|
document the new stuff, partial reorder of options.
|
|
window sizes changes are delayed, nothing to do about it,
since perl keeps the signal around until it is safe to activate it...
|
|
not active unless you specify -x for pkg_add/pkg_delete.
(option is bound to change)
|
