From IRC:
Marjorie: jheiss: is there a way to grab current rather than orig?
jheiss: Not at present
Marjorie: jheiss: I have an entry for the hp-snmp-agents to change the frequency of polling for snmp traffic (causes a load of 1 without it) on 5.3 boxes. The problem is that the newest hp rpm that I needed to use for the dl180G6 servers adds more lines to that file. When I use orig it gets rid of them. For now I'm replacing the old orig with this new file as I don't see any other choice. Suggestions?
jheiss: Seems like it might be a case to stop using orig and write out whole files. I've considered various ways to update orig in this sort of case, where a package update includes a newer "original" file, but I've never come up with a mechanism I felt would be reliable.
Marjorie: jheiss: then we'd have to continuously discover the changes in newer original files and then re-add them. Could we have an "as-is" sort of thing where we just search and replace specific lines in the file regardless of whether it matches orig?
This could either operate via a language for the user to specify edit operations, a la cfengine's ReplaceAll/ReplaceLinesMatchingField/etc., or by adding a mechanism for clients to sometimes or always supply the server with the current file, a la the current mechanism to the supply the server with the original file.
Moved from https://sourceforge.net/apps/trac/etch/ticket/5
From IRC:
Marjorie: jheiss: is there a way to grab current rather than orig?
jheiss: Not at present
Marjorie: jheiss: I have an entry for the hp-snmp-agents to change the frequency of polling for snmp traffic (causes a load of 1 without it) on 5.3 boxes. The problem is that the newest hp rpm that I needed to use for the dl180G6 servers adds more lines to that file. When I use orig it gets rid of them. For now I'm replacing the old orig with this new file as I don't see any other choice. Suggestions?
jheiss: Seems like it might be a case to stop using orig and write out whole files. I've considered various ways to update orig in this sort of case, where a package update includes a newer "original" file, but I've never come up with a mechanism I felt would be reliable.
Marjorie: jheiss: then we'd have to continuously discover the changes in newer original files and then re-add them. Could we have an "as-is" sort of thing where we just search and replace specific lines in the file regardless of whether it matches orig?
This could either operate via a language for the user to specify edit operations, a la cfengine's ReplaceAll/ReplaceLinesMatchingField/etc., or by adding a mechanism for clients to sometimes or always supply the server with the current file, a la the current mechanism to the supply the server with the original file.
Moved from https://sourceforge.net/apps/trac/etch/ticket/5