Release plans

[Stephen J. Turnbull]

Michael Sperber writes:

 > So this is not entirely satisfactory: Doing the right thing would be to
 > detect that `custom-file' points somewhere else, and then leave the
 > custom settings alone.  Does that sound right?

I'm not sure what you mean by "leave them alone."  After a (very)
small amount of thought, I think what I would recommend is

    if user-wants-to-share-init:
        explain why this is a bad idea
        set up load .emacs in ~/.xemacs/init.el
        if custom-file:
            if user-wants-to-share-custom:
                explain why this is a bad idea
                set up load custom-file in ~/.xemacs/init.el
            else if setq custom-file is found:
                disable it
            else:
                warn user
                append '(setq custom-file "~/.xemacs/custom.el") to init.el
        else:
            # normal XEmacs computation of custom-file is safe
            pass
    if user-wants-to-migrate:
        copy original init file to ~/.xemacs/init.el
        if custom-file:
            copy custom-file to ~/.xemacs/custom.el
            if setq custom-file is found:
                disable it
            else:
                warn user
                append '(setq custom-file "~/.xemacs/custom.el") to init.el
        else:
            # normal XEmacs computation of custom-file is safe
            pass
    else if user-wants-new-init-file:
        touch ~/.xemacs/init.el
    else if custom-file:
        warn user
        prompt for new setting (default to nil)