search for: iface2

...> > why doesn't the config file have the version in it ? not having that > makes your whole system error prone. Perhaps I wasn't clear. Version 1 of the package uses a config file that looks like this: system { setting1 value1; setting2 value2; } interfaces { iface1; iface2; } Version 2 of the package has switched to a YAML-based syntax, so the config file needs to look like this: system: setting1: value1 setting2: value2 So, I need to be able to program the RPM so that when upgrading from 1.x to 2.x, it triggers the conversion utility that converts from v1 t...

...in it ? not having that >> makes your whole system error prone. > Perhaps I wasn't clear. Version 1 of the package uses a config file that > looks like this: > > system { > setting1 value1; > setting2 value2; > } > > interfaces { > iface1; > iface2; > } > > > Version 2 of the package has switched to a YAML-based syntax, so the > config file needs to look like this: > > system: > setting1: value1 > setting2: value2 > > > So, I need to be able to program the RPM so that when upgrading from 1.x > to 2...

On 28/06/15 02:17, Joseph L. Casale wrote: > Your script within the rpm should have the logic. Clearly if > you know how to update it, you know how to identify if it > needs updating. Thanks Joseph. I am aware of this option, but it would be only a last resort, because checking the format of the config file is error-prone. I would prefer RPM to tell me the old and new version numbers,

Ok ive been trying to get this to work for about half a year now. Ive searched all over the internet for a solution for my problem. Ive found some solutions, but they only led me to yet more problems. What we want to do is the following: I live in a student complex with 7 other people. Every room has its own internet connection from the same ISP. Ip, gateway, subnet are asigned through dhcp on