Name: Anonymous 2008-03-19 15:38
There's a program made by my employer that is used to configure another program also made by my employer. Currently, the configuration program makes full backups of the configuration file before saving. I thought that this was wasteful, and think that using Git to make backups would save space and make it easy to see what a change actually did.
I wrote a small program in C# that just calls Git to branch, commit, etc. If the programmer for the configuration program decides to incorporate mine, then he'll just execute it like I execute Git. Basically, the configuration program calls backup program which calls Git, but no source code is shared between these programs.
Does /prog/ think that the programs would be "at arm's length," as the GPL FAQ puts it? I don't think that one could consider the configuration program and Git to be merged nor functionally one in any way, but I'd like to hear your opinion.
I wrote a small program in C# that just calls Git to branch, commit, etc. If the programmer for the configuration program decides to incorporate mine, then he'll just execute it like I execute Git. Basically, the configuration program calls backup program which calls Git, but no source code is shared between these programs.
Does /prog/ think that the programs would be "at arm's length," as the GPL FAQ puts it? I don't think that one could consider the configuration program and Git to be merged nor functionally one in any way, but I'd like to hear your opinion.