Yum rollback : Inconsistencies and new ideas !!
The posting of this idea for Gsoc has indeed brought out a lot of defects and inconsistencies in the idea and the proposed implementation , I have been having a good set of discussions with the GSoc mentors , my application doesn't seem to be going anywhere but the idea has been getting a lot of shaping and chiseling, ...... to say in short , there are a lot of shortcomings which were not identified before, and the main drawback was that i had not discussed these ideas with people from the YUM mailing lists, the recent discussions i had on the mailing lists show the following shortcomings, which seem to be very obvious now :
1) the utility would be very slow if it used YUM again for the rollback process also
2) i was suggested to use conventional backup and recovery methods, and try improving the backup storage methods and improve the speed eventually .
3) the system would be left very inconsistent , if the rollback process anywhere involved the use of commands such as 'rpm -e' or 'rpm -e --nodeps, and the second command is even more dangerous .
4) important : the yum log file does not take notice of downgraded changes , which are sometimes done with YUM
5) all the changes done to the system by RPM scripts may not be undone .
one of the changes to the implementation i had proposed was the usage of the systems file database , and the yum repository databases, but now even that seems to be a bad innovations , ..... one things strikes my mind again and again " Ideas are not important , implementation is ", that was actually said by Saifi .
1) the utility would be very slow if it used YUM again for the rollback process also
2) i was suggested to use conventional backup and recovery methods, and try improving the backup storage methods and improve the speed eventually .
3) the system would be left very inconsistent , if the rollback process anywhere involved the use of commands such as 'rpm -e' or 'rpm -e --nodeps, and the second command is even more dangerous .
4) important : the yum log file does not take notice of downgraded changes , which are sometimes done with YUM
5) all the changes done to the system by RPM scripts may not be undone .
one of the changes to the implementation i had proposed was the usage of the systems file database , and the yum repository databases, but now even that seems to be a bad innovations , ..... one things strikes my mind again and again " Ideas are not important , implementation is ", that was actually said by Saifi .
Comments