From f62f37504af51753fcdb9c84fc1846ea8dd90606 Mon Sep 17 00:00:00 2001 From: Aaron Griffin Date: Tue, 20 Feb 2007 08:44:32 +0000 Subject: * Some cascade removal changes. Mainly code cleanup, but this is an attempt to track down the great "Codemac Segfault" * Fixed sortdeps - use the alpm_pkg_get functions to ensure data --- lib/libalpm/add.c | 3 +++ 1 file changed, 3 insertions(+) (limited to 'lib/libalpm/add.c') diff --git a/lib/libalpm/add.c b/lib/libalpm/add.c index 28e66354..a2d79eb4 100644 --- a/lib/libalpm/add.c +++ b/lib/libalpm/add.c @@ -441,6 +441,9 @@ int _alpm_add_commit(pmtrans_t *trans, pmdb_t *db) /* Add files in the NEW package's backup array to the noupgrade array * so this removal operation doesn't kill them */ + /* TODO if we add here, all backup=() entries for all targets, new and + * old, we cover all bases, including backup=() locations changing hands. + * But is this viable? */ alpm_list_t *old_noupgrade = alpm_list_strdup(handle->noupgrade); for(b = newpkg->backup; b; b = b->next) { _alpm_log(PM_LOG_DEBUG, _("adding %s to the NoUpgrade array temporarilly"), (char *)b->data); -- cgit v1.2.3-54-g00ecf