Hi Oren,
Thanks for the reply. Apache Projects can't distribute any source
code that is GPL or LGPL licensed. But we can distribute Apache or
BSD or MIT style licensed source code. We would not be be
distributing Autoconf, but expect our developers to have it installed
prior to building our source code. We could make the same assumption
for your ac_doxygen.m4 too but making someone download and install
that file seperately is a bit annoying for new developers checking
out the project. We were hoping to distribute your ac_doxygen.m4
with our source code to make it easier for them to have Doxygen support.
So is there any chance you could at least dual license that file so
that could include it?
Regards,
Hiram
On Jan 18, 2007, at 3:53 PM, Oren Ben-Kiki wrote:
AFAIK Autoconf itself is released under the GPL. I believe this is
compatible with the Apache license... and at any rate you must include
Autoconf for my code to work, so once you do that, you don't have to
worry about my code.
Let me know if this is a problem, if it is I'm certain we can work
something out. I'll also e-mail [EMAIL PROTECTED] so maybe this will be
added to the official macros list...
Good luck,
Oren Ben-Kiki
On Mon, 2007-01-15 at 21:41 -0500, Hiram Chirino wrote:
Hi Oren,
Thanks for putting together your excellent http://ben-kiki.org/
oren/doxample/ !!
I work on a Messaging product called ActiveMQ. For more info see:
http://incubator.apache.org/activemq/
We want to make use of your ac_doxygen.m4 file to get doxygen to work
with our build but we are not sure what license it available to us
under. It just says:
# Copyright (C) 2004 Oren Ben-Kiki
# This file is distributed under the same terms as the Autoconf
macro files.
But we are not to sure what those terms are. Ideally for us it would
be terms that are compatible with the Apache Software License, which
basically means stuff Apache, BSD, MIT, or other similar licenses.
Please advise as we are want to do a release soon and if we cannot
include your m4 script in our source distribution we need to
remove it
from our repository.
