On Thu, 11 Feb 2010 15:39:48 -0800, Mark Knecht wrote: > Volker is. I am not sure I am and I'm not sure that Neil was talking > about quickpkg which is what I am using so far. The command > > quickpkg --include-configs > > says it includes the configs. That's what I thought we (you and I > Alan) were talking about. > > On the other hand I presumed (apparently incorrectly) that the > FEATURES="buildpkg" (which is what I think Neil is speaking about) > gave me the same option but I now guess it doesn't.
I was talking about the difference between quickpkg and buildpkg in response to your statement "One thing I haven't found so far is what to put in make.conf to get the buildpkg feature to include the configs." So, yes, I was aware of the difference, and the reason why they behave differently. Buildpkg has to work with the files before they are installed, otherwise --buildpkgonly wouldn't work. > If I need to use quickpkg to save the configs then I think I'll do > that being that as I simple-minded home user with no admin experience > I have no in-place rigorous methods for doing __any__ backups. I just > tar up directories once in awhile and deal with the problems that come > later. (If they come...when they come...they do come, don't they?) ;-) What's wrong with a cron job to tar up /etc once per day? There are more sophisticated solutions, but tar does the job and can save you much grief. -- Neil Bothwick Hello, this is an extension to the famous signature virus, called spymail. Could you please copy me into your signature and send back what you were doing last night between 10pm and 3am?
signature.asc
Description: PGP signature
