On 5/26/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > > No, there isn't anything like that yet. Just a few tips, if you're > going to write it yourself: > - Please use the Scripts template, as seen in > /Programs/Scripts/Current/bin/TemplateScript > - Use the $EDITOR variable instead of hardcoding emacs on your > script. If that variable is empty, then I'd suggest you to perform a > simple iteration over /Programs to select which editor to use (ie: > check for Emacs, MC and GVim and Vim to launch 'emacs', mcedit', > 'gvim' and 'vim', respectively. If none are found, ask the user to set > $EDITOR on its $HOME/.profile).
There is the Edit wrapper which tries $EDITOR, mcedit, nano, vi in order. Adding $VISUAL would be nice too. > - Remember to allow more than one file to be specified in the > command line, as it's very usual to have patches composed by changes > to many files. > > You could also require the source code to be uncompressed under > /Files/Compile/Sources. That will help a lot to find the program's > main directory, as there isn't a way to create a sane patch based on > 'AutoPatch /Users/foo/mysources/program/subdir/subdir2/Makefile'). > That makes sense. Doing something similar to quilt [1] might be interesting. [1] http://www.die.net/doc/linux/man/man1/quilt.1.html -- Carlo J. Calica _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
