| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Deprecate INSTALL and DEINSTALL, write out warnings in pkg_create.
Clean up some more old cruft
|
|
|
|
reword the introduction to the stuff originally from FreeBSD to clarify
slightly.
|
|
provided nothing else happens (like, huh, the presence of actual conflicts
between files).
Allows nikolay@ to work with redhat/base and fedora_core at the same time.
|
|
ssh connection for each repository.
|
|
- kill double .Pp
|
|
|
|
Explain about ambiguities, and expand a bit on interactive mode.
|
|
between them a little clearer;
ok espie
|
|
ok espie@
|
|
|
|
noticed by brad@
|
|
uppercase some abbreviations;
|
|
|
|
since pkg_add will have trouble splitting the path correctly in the presence
of weird url schemes otherwise.
|
|
Document a few more -F toggles.
Explain in more details what happens during pkg_add -r.
|
|
|
|
* 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.
|
|
jmc@ insisted... and yeah, it's a bit confusing.
|
|
|
|
|
|
|
|
dependencies as well...
so do the stem -> pkgname conversion early, and then compute the
closure of dependencies on the list of packages we asked for.
|
|
|
|
be scared about -F update.
Document the nasty issues I've encountered with FTP.
|
|
ok espie@
|
|
on the other hand, scp(1) is a pig.
|
|
|
|
from olivier cherrier;
ok espie@
|
|
|
|
|
|
- `-F keyword' -> `-F keywords' in SYNOPSIS for consistency
|
|
okay pvalchev@, naddy@, marco@, deraadt@
(keep -f around for the transition, will scrap it soon)
|
|
not marked with @lib.
This allows pkg_add -current to deal with 3.6 packages fully.
|
|
|
|
|
|
partial-<pkgname>.n if needed.
Make borked_installation take a message, to show installation/deinstallation
issues correctly.
Fix handling of ^C: this may lead some system calls to return early, thus
registering as errors: so always mark the last file as done, so that borked
installation will register it correctly.
Kill packing-list cache for anything but depends: we've got a global cache
of libraries now (use it in pkg_add).
Make almost everyone look at $main::not, so that we can call
register_installation
to_installation
RequirementList->add/delete
safely.
Simplify $not logic accordingly, do thing much more closely to what would
happen without -n.
This should allow pkg_add/pkg_delete -n to handle most nasty cases correctly
now, since all the relevant information is kept internally in a compact
format:
- register of shared libraries
- global register of conflicts
- cache of depends.
|
|
pkg_delete since it now works for both.
|
|
espie@ ok.
|
|
ok espie@
|
|
ok espie@
|
|
changes over time.
|
|
document the new stuff, partial reorder of options.
|
|
only DEINSTALL or @unexec (we should need to run symetric checks on
the package we're going to install, though...)
allows forced replacement: script running, and breaking forward dependencies.
Communicate more about what may break.
|
|
Clearly marks this as an experimental option that can thoroughly mangle
your system.
|
|
|
|
Common option for not running scripts: -I for both pkg_add and pkg_delete.
|
|
kill -C and -P options which are definitely no longer used as well.
Reorder special files so that REQUIRE is at front (and it's executed first
anyways).
|
|
wanted by the user) from packages installed automatically to satisfy a
dependency.
|
