[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Savannah-hackers] submission of BitBake build tool - savannah.nongn
Jonathan Gonzalez V.
Re: [Savannah-hackers] submission of BitBake build tool - savannah.nongnu.org
Sat, 04 Dec 2004 12:12:25 -0300
Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux)
Chris Larson <address@hidden> writes:
Hi Chris Larson,
I reviewed your source code, and you have the Copyright Notices
missing in some files, and the License Notices too in other files, fix
this issue. Keep in mind that any file with more than 10 lines should
carry on a Copyright and License Notices, this rules include shell
scripts(.sh) Makefiles(generated by hand), etc. If you have doubts
about where and when put the Copyright and License Notices, read these
On the other hand, was a little hard define where is your source code
and where is the dependencies code on the tarball, you should keep the
dependencies out of your tarball, this will keep your source code
clean and the users can change the dependencies without change the
source code itself.
> * Jonathan Gonzalez V. (address@hidden) wrote:
>> Can you give me a list of all the projects dependencies and the
>> language programming you will use?
> The current incarnation is written in python, and requires at least
> version 2.3 to function. Python, then, is its only real dependency.
>> On the other hand, can you send me the source code project to my email
>> account (address@hidden)? I wish to review your source code,
>> even if it is not functional, to catch potential legal issues early.
> I've attached the current incarnation of the code. Currently, the
> beginning of each file references the COPYING files in the doc/ dir in
> the source tree. If this isn't sufficient, let me know.
> The next incarnation (version 2.0, which will be under way shortly) is
> to be written in C, but you needn't worry about that yet.
>> For example, to release your program properly under the GPL you must
>> include a copyright notice and permission-to-copy statements at
>> the beginning of every file of source code. This is explained in
>> http://www.gnu.org/licenses/gpl-howto.html. Our review would help catch
>> potential omissions such as these.
> Great, your review will certainly help. I should mention that the
> included metadata (configuration files, bbclasses with tasks to execute)
> is licensed under MIT.
>> > A package was submitted to savannah.nongnu.org
>> > This mail was sent to address@hidden, address@hidden
>> > Chris Larson <address@hidden> described the package as follows:
>> > License: gpl
>> > Other License:
>> > Package: BitBake build tool
>> > System name: bitbake
>> > Type: non-GNU
>> > Description:
>> > BitBake is a simple tool for the execution of tasks/recipes. It is derived
>> > from Portage, which is the package management system used by the Gentoo
>> > Linux distribution. It is most commonly used to build packages, as it can
>> > easily use its rudamentary inheritence to abstract common operations, such
>> > as fetching sources, unpacking them, patching them, compiling them, and so
>> > on. It is the basis of the OpenEmbedded project, which is being used for
>> > OpenZaurus, Familiar, and a number of other Linux distributions.
> Chris Larson - kergoth at handhelds dot org
> Linux Software Systems Engineer - clarson at ti dot com
> OpenZaurus Project Maintainer - http://openzaurus.org/
"Emacs the only editor which has its own church"
Description: PGP signature