On Fri, Dec 23, 2005 at 11:43:04AM +0100, Jerome Warnier wrote: > Package: cedar-backup2 > Version: 2.7.2-1 > Severity: wishlist > > Could you please already adapt the sample configuration file to Debian. > I think particularly to pathes to utilities like cdrecord, mkisofs, ...
Many Debian packages just include upstream sample configuration files verbatim, and do not adapt these files to Debian. That is because, like in Cedar Backup, these samples files are not supposed to be typical or representative, just informative. In other words, they are a starting point (perhaps just to provide an example of appropriate syntax), and are not intended to represent real working configuration. In this case, the Cedar Backup sample file includes examples of nearly every type of configuration section (for reference) but in a form and in a combination that probably no one will ever use. I resist providing any "real" sample configuration because everyone's system is different. The documentation is really the source you should be going to as you try to build your configuration file. Or, write the upstream user mailing list if you have configuration questions (and yes, you'll probably talk with me there as well, but that's not the point). Incidentally, in this particular case, I wouldn't want to adapt the override paths to a Debian system, because that would mean removing them entirely from the sample. They're not required on a standard Debian system. KEN -- Kenneth J. Pronovici <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
