Randy McMurchy wrote: > Alexander E. Patrakov wrote these words on 08/16/07 00:51 CST: > > >> Slackware packages never ship configuration files that are supposed to >> be modified by end users. Instead, such configuration files are shipped >> with the .new extension, and a post-installation script handles this. >> > > This to me is way, way beyond the scope of what we do. If it ends up > that we want to do something like this, I would hope it would be a > separate branch, with the main thrust continuing with what we > currently do. >
Sure. We won't do this, because this is specific to Slackware package manager. My intention was to demonstrate to Bruce how this works, not to suggest this for the book as a mandatory part. Other package managers have a different approach to handling configuration files. E.g., RPM and dpkg support them natively, provided that they are marked as such in the spec file or listed in the debian/conffiles file. However, we should do a common part that applies to all package managers: for each package, identify and list (as we do, e.g., for installed libraries) configuration files (i.e., files that are supposed to be changed after installation by the end user or by a script that comes with a package). -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
