You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apr.apache.org by "William A. Rowe, Jr." <wr...@rowe-clan.net> on 2009/02/24 04:47:04 UTC
Re: svn commit: r747266 - in /apr/apr/branches/1.3.x: ./ CHANGES
build/ buildconf configure.in
bojan@apache.org wrote:
> Author: bojan
> Date: Tue Feb 24 03:24:54 2009
> New Revision: 747266
>
> URL: http://svn.apache.org/viewvc?rev=747266&view=rev
> Log:
> Backport r733052 from the trunk.
> Fix buildconf with libtool 2.2:
>
> * buildconf: Use a different Extremely Ugly Hack to extract and copy
> the list of .m4 files needed directly from libtoolize.
>
> * configure.in: Include more files which might be needed by libtool.
stupid question, but did you validate the licensing implications of
this particular commit?
Re: svn commit: r747266 - in /apr/apr/branches/1.3.x: ./ CHANGES
build/ buildconf configure.in
Posted by Bojan Smojver <bo...@rexursive.com>.
On Tue, 2009-02-24 at 15:57 +1100, Bojan Smojver wrote:
> I'll check before the release.
argz.m4:
----------------------------
# This file is free software; the Free Software Foundation gives
# unlimited permission to copy and/or distribute it, with or without
# modifications, as long as this notice is preserved.
----------------------------
ltoptions.m4:
----------------------------
# This file is free software; the Free Software Foundation gives
# unlimited permission to copy and/or distribute it, with or without
# modifications, as long as this notice is preserved.
----------------------------
ltversion.m4:
----------------------------
# This file is free software; the Free Software Foundation gives
# unlimited permission to copy and/or distribute it, with or without
# modifications, as long as this notice is preserved.
----------------------------
lt~obsolete.m4:
----------------------------
# This file is free software; the Free Software Foundation gives
# unlimited permission to copy and/or distribute it, with or without
# modifications, as long as this notice is preserved.
----------------------------
So, I think we should be good.
--
Bojan
Re: svn commit: r747266 - in /apr/apr/branches/1.3.x: ./ CHANGES
build/ buildconf configure.in
Posted by Bojan Smojver <bo...@rexursive.com>.
On Mon, 2009-02-23 at 22:14 -0600, William A. Rowe, Jr. wrote:
> But did you check what
> this step now absorbs into the finished package?
No, not really. I'll check before the release. In the meantime, it's in
SVN, which should be OK.
Not sure if this may be relevant:
http://www.gnu.org/software/autoconf/manual/autoconf.html#Distributing
PS. This same revision was backported to 1.4.x as well by Jim. So, if we
release 1.4.x before 1.3.x, same thing applies.
PPS. Is this what we are looking for (example from ltmain.sh distributed
with apr-1.3.3):
-----------------------
# As a special exception to the GNU General Public License, if you
# distribute this file as part of a program that contains a
# configuration script generated by Autoconf, you may include it under
# the same distribution terms that you use for the rest of that program.
-----------------------
--
Bojan
Re: svn commit: r747266 - in /apr/apr/branches/1.3.x: ./ CHANGES
build/ buildconf configure.in
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Bojan Smojver wrote:
> On Mon, 2009-02-23 at 21:47 -0600, William A. Rowe, Jr. wrote:
>
>> stupid question, but did you validate the licensing implications of
>> this particular commit?
>
> Not sure what you mean. Is our trunk licensed differently than 1.3.x?
No, but I'm just checking; this step absorbs local files... ergo
the finished bundle doesn't resemble svn. Trunk is svn. We tolerate
transitory GPL licenses in our build process. But did you check what
this step now absorbs into the finished package?
Re: svn commit: r747266 - in /apr/apr/branches/1.3.x: ./ CHANGES
build/ buildconf configure.in
Posted by Bojan Smojver <bo...@rexursive.com>.
On Mon, 2009-02-23 at 21:47 -0600, William A. Rowe, Jr. wrote:
> stupid question, but did you validate the licensing implications of
> this particular commit?
Not sure what you mean. Is our trunk licensed differently than 1.3.x?
--
Bojan