Remove REQUIREDBY usage from libalpm

Instead of using the often-busted REQUIREDBY entries in the pacman database,
compute them each time they are required. This should help many things:

1. Simplify the codebase
2. Prevent future database corruption
3. Ensure when we do use requiredby, it is always correct
4. Shrink the pmpkg_t memory overhead

Signed-off-by: Dan McGee <dan@archlinux.org>

1 files changed, 0 insertions, 7 deletions

diff --git a/lib/libalpm/add.c b/lib/libalpm/add.c
index 277293f6..d242134a 100644
--- a/lib/libalpm/add.c
+++ b/lib/libalpm/add.c
@@ -804,10 +804,6 @@ static int commit_single_pkg(pmpkg_t *newpkg, int pkg_current, int pkg_count,
 		}
 	}
 
-	/* Update the requiredby field by scanning the whole database
-	 * looking for packages depending on the package to add */
-	_alpm_pkg_update_requiredby(newpkg);
-
 	/* make an install date (in UTC) */
 	newpkg->installdate = time(NULL);
 
@@ -827,9 +823,6 @@ static int commit_single_pkg(pmpkg_t *newpkg, int pkg_current, int pkg_count,
 				alpm_pkg_get_name(newpkg));
 	}
 
-	/* update dependency packages' REQUIREDBY fields */
-	_alpm_trans_update_depends(trans, newpkg);
-
 	if(is_upgrade) {
 		PROGRESS(trans, PM_TRANS_PROGRESS_UPGRADE_START,
 				alpm_pkg_get_name(newpkg), 100, pkg_count, pkg_current);