23 May
2007
23 May
'07
10:44 a.m.
Hm, seems that this approach is still not quite usable. Let's have another try:
Each project release gets an additional "External library tarball" upload field, which takes either .tar.gz or .tar.bz2 files, and on creating the release this file is unpacked into the module's root folder. After creating the release, the file can not be changed anymore.
I just posted a comment on this about CVS internal ability to manage third party code - vendor branches. http://drupal.org/node/124978#comment-234594 --yuval