Re: Image versus package savers?

Griff wrote:
As far as version control for applications within in your image, would
you say that you prefer backing up your whole image frequently and
exporting then backing up your packages frequently, or vice versa?

If you are using Subversion to do so, do you keep two separate
repositories: one for mostly binaries (like system images, graphical
images) and one for primarily text files (exported packages, text
files)?

If you search for the keyword "bonkers" (sorry Andy - it's just the easiest way to find the thread), you will find some healthy debate on the subject. I tend to use an image for a very long time, _but_ I have some fairly strict rules for when to abandon w/o saving. Knowing that, I set up to try something risky (see below), save, and then give it a shot. If all DLL breaks loose, then I learn what I can in the debugger and bail out, hopefully fixing it in the freshly reloaded image. Others build a new image from packages every day (sometimes more frequently).

Things that I consider risky include: newly changed external interfacing; failure of an MVP triad to open correctly; note that you should never save an image if the dreaded prim g2 garbage collector (or whatever it's called) walkback appears. The latter might not apply in D6??

An obvious advantage of building frequently is that you will discover and fix install script oversights.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
bills@xxxxxxxxxxxxxxxxxxxx
.

Relevant Pages

  • More Multiple Classes per File (was Pretty Format...)
    ... Uri Guttman wrote: ... setups to exercise the limits of these paradigms. ... I think key to all of this is that packages that contain subs intended ... exporting no symbols with EXPORTER. ...
    (comp.lang.perl.misc)
  • Re: Understanding CLOS Encapsulation
    ... exporting a class name only exports the symbol. ... accessor functions. ... class may have slots from different packages. ... it is not clear which one you would want to simply refer to as SLOT-X ...
    (comp.lang.lisp)
  • Re: Help with packages
    ... to use from outside the package implementation fileneeds to be ... Exporting applies only to SYMBOLs. ... symbol FOO means that both ... Packages in lisp are only there to prevent accidental namespace ...
    (comp.lang.lisp)
  • Re: CSTD=c99 breaks package creation
    ... > Backing out the recent changes to bsd.sys.mk fixed these problems. ... but pkg_create was creating packages that were ... > standards. ... If you can wait until after USENIX, ...
    (freebsd-current)
  • Re: Read Macro Characters and Packages
    ... I don't have the impression that changing the read table occurs so often that ... My guess would be that exporting ... wondered if perhaps the import itself was considered explicit enough. ...
    (comp.lang.lisp)