hi,Arthur: I guess it's a little tricky. But still there's way to solve that, this seems like the final obstacle. When you start a new project in Anjuta, there's declaration you can choose which license you are willing to use to this project: GPL/LGPL/BSD or totally free. If we just change the license to BSD or free, i guess everything is ok. i just test to create two project with GPL license and free license seperately. and the difference is that there's GPL license declaration in source files under /src directory. I am not familar with Anjuta but i guess we could change the property of the project license to Free. i will consult that on the mailing list of Anjuta or refer through google. The only thing troubles is the sh files like libtoo.sh which i believe that generated by Anjuta automaticly when building the whole project. There's might no way to cut the GPL declaration but to re-build the whole project under free license. That's my opinon so far, but we could dig in to see whether there is another way. regards, Kevin
2009/9/22 Arthur Chen <[email protected]> > Hi all, > > The license problem of source code is solved almost. Kevin and I are trying > list the project systematically, > but we encountered another kind of license problem. I am a little confused > about it. > > The Realclass system project was build and compiled in Anjuta. To make the > compile process simple and easy, > Anjuta add some bash scripts which are executed to set the compile > environment suitable for Realclass system. > But Anjuta is a GPLed IDE, thus I am not sure about the license of those > files (auto generated by Anjuta ) > Can we submit these files together with source code? > > Best regards, > Arthur > -- Bowen Ma a.k.a Samuel Kevin @ Bluesky Dev Team XJTU Shaanxi Province Key Lab. of Satellite and Terrestrial Network Tech http://incubator.apache.org/bluesky/
