While not even thinking about packaging stuff, I'm still fond of automating things, like building a new image. The bootstrap ends with the pristine factor.image, a well-defined starting point, to be kept for reference.
My work usually starts from a "virgin" image with a basic environment preloaded, but only the tiniest bit of stuff that might break. git pull rm boot.unix-x86.64.image make clean make wget http://factorcode.org/images/latest/boot.unix-x86.64.image ./factor -i=boot.unix-x86.64.image chmod a-w factor.image ./factor -i=factor.image -e='USING: system memory ; IN: scratchpad : bye ( -- ) 0 exit ; "virgin.image" save-image-and-exit' At this point I can ./factor -i=virgin.image and rely on my forth-based muscle memory to exit via bye :-) Suggestions for improving this? Thanks, s. ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
