What's the logic for having updates erase all manually installed RPMs? A couple of Support-Gangers and myself were talking about ways to remedy this. We came up with the following:
- alias "rpm -i $FILE" to "rpm -i $FILE & cp FILE $HOME/.rpms$/FILE" with a script on update that runs "rpm -i $HOME/.rpms/*" - have a script that constantly monitors $HOME/.bash_history for "yum install $PROGRAM" formatted files, then echos the name of $PROGRAM to $HOME/.rpms/installed, but removes it from that list if/when it sees "yum remove $PROGRAM" On update, yum install $(cat $HOME/.rpms/installed) is run. - rpm -qa > $HOME/.rpms/clean could be run on install - rpm -qa > $HOME/.rpms/custom could be run before update - a simple file compare program (python or python-parsed diff output) would be used to generate a file with which yum install $(cat $FILE) could be used thoughts? -- Ian Daniher -- OLPC Support Volunteer OLPCinci Repair Center Coordinator -- [EMAIL PROTECTED] Skype : it.daniher irc.freenode.com: Ian_Daniher
_______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel