The proposed change to the operation of the xs-config package seem sane, with a few comments:
The make-a-replacement strategy is the crucial one. I have hesitations about the xs-config.make file used: - Multiple will be needed, in each directory with changed files. - Getting a correct config now requires a correct make file and a correct ".in" file (plus helpers) for each file generated. - It lumps together changes for multiple packages It doesn't fix the problem with user changes being deleted --- the *.in file will change and a new file will be generated overwriting previous configuration. What did I miss ? wad _______________________________________________ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
