Send patches - preferably formatted by git format-patch - to patches at archlinux32 dot org.
summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorAurelien Foret <aurelien@archlinux.org>2006-01-10 22:09:47 +0000
committerAurelien Foret <aurelien@archlinux.org>2006-01-10 22:09:47 +0000
commitc305bf670bf48c39f0459f4c26688d11ad7a4b25 (patch)
tree7b4891d9388b85a0d925dbcf2a60b61970e51df4 /README
parent540d3d49b22fafdbdc9fa2e30eff572f71144b3a (diff)
updated README and download comments about mtimes support
Diffstat (limited to 'README')
-rw-r--r--README22
1 files changed, 0 insertions, 22 deletions
diff --git a/README b/README
index 57b9d325..b9a627c7 100644
--- a/README
+++ b/README
@@ -268,25 +268,3 @@ Single chained list.
A minimalistic chained list implementation to store options from the
configuration file, and targets passed to pacman on the command line.
-
-LIMITATIONS/BEHAVIOR CHANGES COMPARED TO PACMAN 2.9
-===================================================
-
-Excepted missing features still needing to be implemented, one can
-notice the following limitations:
-
-- When trying to add a package that conflicts with an already installed
-one, pacman won't ask for removing the latter one prior to install the
-former.
-It will stop with an error code mentionning a conflict.
-
-The library can handle only one transaction at a time, and as a consequence,
-it is not easily possible to remove a conflicting package while holding
-still the on-going transaction...
-
-- If pacman is out of date, the frontend displays a warning and recommends
-to give up the on-going transanction. The frontend does not allow to
-upgrade pacman itself on-the-fly, and thus it should be restarted with
-only "pacman" as a target.
-
-- ...