Changing topic to avoid polluting the vote. On Sat, Feb 11, 2017 at 7:09 PM Justin Mclean <jus...@classsoftware.com> wrote:
> Hi, > > > The problem I see is how autoconf files are actually applied with their > > headers and licenses. > > Interesting. So are you saying it would be OK to remove the original > license headers and replace it with an ASF one? > > That's effectively what the license is saying to do, as long as you're meeting the requirements. Note - its very hard to meet these requirements outside of build chains I would imagine, since you're limiting derivative software. > > If I look within HTTPD for instance there's no headers > > Like this file [1]? :-) Not Autoconf but aa build tool and the same GPL > exception. > > That's an interesting one. I'm a bit surprised if that would be considered OK for this scenario. Sure, HTTPD is usually used as a standalone server. What happens if you embed HTTPD in your own data parser? You're effectively violating that license. This specific case seems very Cat-X to me. Similar to the JSON license "no evil" clause. I actually don't see how this is a build tool (though its been 5 years since I've had to deal with make). > BTW There a fair number of incubating and TLPs containing files with GPL > exception headers. [2] > > Most of those are OK, if you look they're autoconf, and notice declarations. Granted I only skimmed the first 2 pages. > Thanks, > Justin > > 1. > https://github.com/apache/httpd/blob/fbc5e20ead005fd3a2bec05924f9e90dfd195406/server/util_expr_parse.h > 2. > https://github.com/search?utf8=✓&q=org%3Aapache+%22As+a+special+exception%22&type=Code&ref=searchresults > <https://github.com/search?utf8=%E2%9C%93&q=org%3Aapache+%22As+a+special+exception%22&type=Code&ref=searchresults> > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
