Re: [Patch] Forcibly copy scripts to overwrite .svn files

["Kris Katterjohn" <katterjohn () gmail com>]

On 5/18/07, David Fifield <david () bamsoftware com> wrote:

> Right, I know that "export" can do that, but I hadn't thought of
> exporting the working copy every time I update it as part of normal
> development. Shouldn't it work to build and install from the working
> copy? How is everyone else doing it?
>
> I'll admit that this is a very specific use case, affecting only
> developers, but adding the -f shouldn't hurt in any case. That's what
> the "install" command does anyway when it's installing all the other
> files.
>
> David
Well I wasn't saying -f was a bad idea, just suggesting export.

I have an "svn" directory with the "nmap", "nmap-exp", etc. subdirectories
in there.  I also have a "work" directory that holds exported directories
for when I'm testing a patch, or wanting to install an updated version.  I
don't tend to install a new version of Nmap unless it's a pretty big change
that I want (or after a quite a few revisions just because), so exporting it
everytime isn't a problem for me.

That leaves completely clean SVN directories, and exported ones for me to
mess with.


Thanks,
Kris Katterjohn

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org