Automatic generation of patches.

From: Hal Niner (hal9_at_cyberspace.org)
Date: 10/31/03 

Date: 31 Oct 2003 09:42:05 -0800

I'm looking for a automatic way of generating files that patch a live
running system. My idea is: I have (a) an old source code (b) a new
source code. Somehow I want to generate a file containing the
difference between (b) and (a) that can be (LOAD)ed into a running
lisp system. Ideally this file would containg only the minimal
changes needed to upgrade the live system.

Relevant Pages

  • Re: Automatic generation of patches.
    ... >>I'm looking for a automatic way of generating files that patch a live ... Somehow I want to generate a file containing the ... > But that will only help you with finding differences in source code, ... > for a useful patch you will need more. ...
    (comp.lang.lisp)
  • Re: Video editing in Linux?
    ... >> this is an absolute world of difference from windows. ... but theres so much to take in just to install an audio app. ... I was under the impression that you sent the source code and a patch ...
    (alt.linux)
  • Re: Updates vs. patches
    ... > security updates with something like apt, ... A patch assumes you've compiled and installed a program from source code. ... program), compile and install again. ...
    (comp.os.linux.security)
  • Re: Network Manager Patch
    ... Understand, I look at the patch, I see source code, and wonder ... That means with the old version and the patch, ... mkdir NetworkManager ... const struct iw_quality *max_qual, ...
    (Ubuntu)
  • Re: [ANNOUNCE] Release Digsig 1.3.1: kernel module for run-time a uthentication of binaries
    ... We integrated Chris's patch to our cvs source code base. ... > #ifdef DIGSIG_REVOCATION ... > * public key to use to verify ELF file signatures. ...
    (Linux-Kernel)