i don't get the point of this discussion! isn't it the devs choice to do it how _he_ thinks it's good and reasonable? if thomas thinks putting a sed line in the .install is the best way, then he should do it! On Sun, Jul 19, 2009 at 12:57:30PM +0200, Thomas Bächler wrote: > Pierre Chapuis schrieb: >> That teaching might require breaking the system of those that don't follow simple rules such as read the output of Pacman. > > How can a user distinguish between important pacman output and the crap > that is put everywherre? > >> Moreover, I have modified /etc/inittab, and depending on what the sed does, it might break my system. I don't think I'm the only user to have done that. So, even if you go the sed way, you will need to use post_upgrade() to warn the users that you changed something, and probably create a .pacsave... But in fact, if your goal is to make the systems of people who don't know what /etc/inittab is work, why use sed and not just replace the file with a new one using tty? > > There was the time when pacman saved the old file as .pacsave and put > the new one in place, effectively restoring the default configuration > and leaving it to the user to merge in his custom configuration. I am > beginning to understand why someone would do it this way. yes, creating a pacsave file is an elegant solution. vlad --
