Seems like module maintainers could just "officially" incorporate GPL code into their module, meaning they will support it (hopefully including contributing bug reports and patches "upstream"). Thus it's no longer "third-party code," it's part of the drupal module which they are maintaining.
<br><br>I wouldn't consider this "ideal".. but it would be a major task to build something like "drupal ports", where tarballs are downloaded from the vendor and then patch files are applied if necessary.
<br><br>speaking of which, it's interesting that on freebsd you can install drupal tinymce module from ports, <a href="http://www.freshports.org/www/drupal5-tinymce">http://www.freshports.org/www/drupal5-tinymce</a>, which depends on tinymce
<a href="http://www.freshports.org/www/tinymce">http://www.freshports.org/www/tinymce</a> (tinymce is downloaded from sourceforge if you "build" it), and symlinks the server-wide tinymce into the drupal module directory. I happen to use freebsd but hadn't given much thought about using it to manage the installation of drupal modules..
<br><br>--mark<br><br><div><span class="gmail_quote">On 5/27/07, <b class="gmail_sendername">Walt Daniels</b> <<a href="mailto:wdlists@optonline.net">wdlists@optonline.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
+100 on this<br><br>It is trivial to implement just change the policy (but add a pretty please<br>permission somewhere in the process).<br><br>-----Original Message-----<br>From: <a href="mailto:development-bounces@drupal.org">
development-bounces@drupal.org</a> [mailto:<a href="mailto:development-bounces@drupal.org">development-bounces@drupal.org</a>]<br>On Behalf Of Derek Wright<br>Sent: Sunday, May 27, 2007 4:12 AM<br>To: <a href="mailto:development@drupal.org">
development@drupal.org</a><br>Subject: Re: [development] Drupal's CVS policies... including 'foriegn'<br>codein TinyMCE module?<br><br><br>On May 26, 2007, at 9:29 PM, Boris Mann wrote:<br><br>> A patch to the project module / packaging scripts and/or an
<br>> architecture doc on how such a thing would be built would be more<br>> useful.<br><br>(trying not to lose my temper...)<br><br>WTF? are you people not getting or not reading my messages? Gerhard seems<br>to have completely ignored my input on the discussion, and now you are,
<br>too...<br><br>how many times do i have to say it?<br><br>1) our existing policy is too strict, and should be relaxed under some<br>circumstances.<br><br>2) it would require a *MASSIVE* (wasted) effort to try to solve this problem
<br>via modifying our packaging script. please RTF previous email of mine for<br>details. i will *NOT* accept patches that attempt to do this. "won't fix"<br>on sight...<br><br>so, of all the many ways i've asked for help on project*, please do not try
<br>to "help" by working on such a patch. ;)<br><br>also, given how much time and energy i've spent on the care and feeding of<br>our CVS repositories, i wish i was at least being taken seriously enough<br>that people read what i'm saying about this topic, and respected my views
<br>enough to reply (even if you disagree, at least address the points i'm<br>making)...<br><br>thanks,<br>-derek<br><br><br><br><br>--<br>No virus found in this incoming message.<br>Checked by AVG Free Edition.<br>Version:
7.5.472 / Virus Database: 269.8.0/819 - Release Date: 5/26/2007<br>10:47 AM<br><br><br></blockquote></div><br>