Hi, If i am not mistaken FS#8585 deals with transactions and rollback and in case something errors out its rolled back. But here i was trying to make a backup for all those people who complain during every kernel update that they had cleaned their cache and then want to roll back to the previous version.
I saw FS#11913 on the bugtraker which was a request for this feature and it seemed easy to implement. Jatheendra On Fri, Nov 7, 2008 at 5:52 PM, Nagy Gabor <[EMAIL PROTECTED]> wrote: >> Hi all, >> Im trying to add some downgradability magic into pacman .Being quite >> new to pacman code, i need your help to identify the possible >> pitfalls of my approach before trying something. >> >> What i plan to do is.. >> >> In libalpm/remove.c unlink_file() [ I guess remove.c is the only >> place where we are removing files ] >> >> replace all unlink(), rename() etc with copyandunlink , copyandrename >> etc which will copy the file first into an archive file >> package-backup.tgs in cache,then do unlink or rename. Then finally >> include all the necessary .INSTALL ,PKGINFO ,.CHANGELOG etc and clean >> up. >> >> So even if i do a -Scc i will have a backup of what was installed on >> my system and can roll back to the previous state. > > I suggest you implementing FS#8585 ;-) > >> And can sombody please point me to some documentation for libarchive >> apart from the manpages... >> > > http://code.toofishes.net/ > and README file in git tree. > > Bye > > > ------------------------------------------------------ > SZTE Egyetemi Konyvtar - http://www.bibl.u-szeged.hu > This message was sent using IMP: http://horde.org/imp/ > > > _______________________________________________ > pacman-dev mailing list > [email protected] > http://archlinux.org/mailman/listinfo/pacman-dev > _______________________________________________ pacman-dev mailing list [email protected] http://archlinux.org/mailman/listinfo/pacman-dev
