summaryrefslogtreecommitdiff
path: root/po
diff options
context:
space:
mode:
authorPanu Matilainen <pmatilai@redhat.com>2008-03-17 14:10:11 +0200
committerPanu Matilainen <pmatilai@redhat.com>2008-03-17 14:10:11 +0200
commitd89482a7c7777d379ab415ebba747b6af19babdb (patch)
tree086729e83518cbac0b829f6cb8d6e7054ebcead4 /po
parent37543ee0405c38a9d54a12bf0d54698773a3933c (diff)
downloadlibrpm-tizen-d89482a7c7777d379ab415ebba747b6af19babdb.tar.gz
librpm-tizen-d89482a7c7777d379ab415ebba747b6af19babdb.tar.bz2
librpm-tizen-d89482a7c7777d379ab415ebba747b6af19babdb.zip
Remove repackage support to finish off with rollback
The two main classes of rollback/repackage need are 1) Gimme back the previous version, this broke XYZ on my system. This is better handled by downgrading to the previous version of original package instead of repackaged garbage. We should maintain real package (version) history somewhere. 2) Upgrade messed up my configuration. Instead of repackaging everything we could be far more intelligent wrt config files, stick them into real version control or at least have hooks to do so. RPMCALLBACK_REPACKAGE_* and RPMTRANS_FLAG_REPACKAGE definitions left around to avoid needlessly breaking everybodys callbacks (for now)
Diffstat (limited to 'po')
0 files changed, 0 insertions, 0 deletions