Is there a library containing just the option and subcommand processing code from git? I saw a post about gitopt but can't find a project with that name. If not is there any problem with me doing this? Thanks.
- Mike Bergin
threads / discuss / 20228
Subject: Git Option/Subcommand Processing Library?
Is there a library containing just the option and subcommand processing code from git? I saw a post about gitopt but can't find a project with that name. If not is there any problem with me doing this? Thanks.
- Mike Bergin
Re: Git Option/Subcommand Processing Library?
Hi,
On Sat, 25 Jul 2009, Michael Bergin wrote:
> Is there a library containing just the option and subcommand processing > code from git? I saw a post about gitopt but can't find a project with > that name.
The "library" is contained in the files parse-options.[ch] in git.git. I am unsure if you need strbuf.c, too, or not.
> If not is there any problem with me doing this?
Not if you abide by the license of git.git, which is GPLv2.
Ciao, Dscho
Re: Git Option/Subcommand Processing Library?
Thanks for the pointers. I also want to create a generic library for command facades like git. For that I will probably use git.c as a guide but to make it generic I would need to add/rearrange code. GPLv2 works fine for my purposes. I hope this isn't an offensive question or anything but would releasing just the library under LGPL be considered?
On Jul 25, 2009, at 12:32 PM, Johannes Schindelin wrote:
> Hi, > > On Sat, 25 Jul 2009, Michael Bergin wrote: > >> Is there a library containing just the option and subcommand >> processing >> code from git? I saw a post about gitopt but can't find a project >> with >> that name. > > The "library" is contained in the files parse-options.[ch] in > git.git. I > am unsure if you need strbuf.c, too, or not. > >> If not is there any problem with me doing this? > > Not if you abide by the license of git.git, which is GPLv2. > > Ciao, > Dscho > >
Re: Git Option/Subcommand Processing Library?
Hi,
On Sat, 25 Jul 2009, Michael Bergin wrote:
> Thanks for the pointers. I also want to create a generic library for > command facades like git. For that I will probably use git.c as a guide > but to make it generic I would need to add/rearrange code. GPLv2 works > fine for my purposes. I hope this isn't an offensive question or > anything but would releasing just the library under LGPL be considered?
You need to ask all authors of all the code you reuse. I, for one, have no objections.
Ciao, Dscho
Re: Git Option/Subcommand Processing Library?
I really appreciate your help. I'm going to do this regardless of license so I'll ask about that when I have a finished project. Let me know if you have any suggestions for features, etc. Thanks again.
- Mike Bergin
On Jul 25, 2009, at 7:18 PM, Johannes Schindelin wrote:
> Hi, > > On Sat, 25 Jul 2009, Michael Bergin wrote: > >> Thanks for the pointers. I also want to create a generic library for >> command facades like git. For that I will probably use git.c as a >> guide >> but to make it generic I would need to add/rearrange code. GPLv2 >> works >> fine for my purposes. I hope this isn't an offensive question or >> anything but would releasing just the library under LGPL be >> considered? > > You need to ask all authors of all the code you reuse. I, for one, > have > no objections. > > Ciao, > Dscho