On Nov 9, 2007, at 15:16, Landon Fuller wrote:
On Nov 8, 2007, at 08:58, Emmanuel Hainry wrote:Dear list, For a port I maintain (namely rubber), there are some patchesthat upstream has not yet included and are provided by the maintainer ofthe port for pkgsrc. They are now in macports repository and I wonderwhich license if any is applied to patches (as Trac.macports.org tells people that what they put here is automatically under the Apache or BSD License). Is there a way to credit the author of a patch and to cite thelicense they may be under? This problem (but is it a problem?) is, I think, not a rare thing: the work of preparing a program to be part of a ports project is verysimilar between pkgsrc, openBSD, freeBSD and macports (maybe gentoo andother linux source based packages too) and hence reusing patches from others is highly probable.For what it's worth, it's my assumption that any patches I write are licensedunder the same license as the project.
Er, I should clarify. Licensed under the same license as the project *that I'm patching*.
-landonf
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
