Re: [pygccxml-development] [release] setup.py need to be updated

[Roman Y. <rom...@gm...>]

On 8/23/06, Matthias Baas <ba...@ir...> wrote:
> Roman Yakovenko wrote:
> > Hi. Matthias and Allen, I hope I will be ready to release Py++ next week.
> > I would like to distribute contrib package too. There is small amount
> > of work that should
> > be done:
> >
> > 1. To update setup.py script: to add your packages and generate documentation.
>
> I did that already when I was adding the contrib directory to the
> repository (actually it's not the setup.py script that I had to modify
> but the MANIFEST.in file).
> So when you create a source distribution the contrib directory should
> already be part of it.

I see, what about documentation? Don't you want to integrate to
setup.py script to build
pypp_api documentation?

> > 2. License. Not all files/directories contains license.
>
> I added a short license information to pypp_api (but I don't think we
> have to be too picky here. I'm sure that every contributor who adds
> something to contrib doesn't have any objections when you redistribute
> that code with the Py++ sources. I couldn't imagine that someone is just
> adding code so that he can sue you as soon as you release that code... ;)

I thought about different situation: there are people and\or
organization, that just can
not use the code, if license is not clear or it is not XYZ. This is
the only reason.

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/