On Feb 16, 2012, at 12:33 PM, Jakob Sack wrote: > Hi, > > I suggest the following solution: > - create a repository for 3dparty resources, called "owncloud-3dparty" > - add the 3dparty-folder to the load path: > a) If defined in config.php then use this path > b) look for 3dparty in base directory > c) look for "owncloud-3dparty" in parent directory > d) die if the 3dparty-folder is not found > > I think that this is a good approach because: > 1) ownCloud and 3dparty are not in one repository > 2) ownCloud will run after "git clone owncloud && git clone owncloud-3rdparty" > 3) ownCloud runs if you copy/symlink the 3dparty folder to the base path > 4) distributions can put the 3dparty stuff everywhere and adapt the default > config.php to the changes > > The only disadvantage I can see right now is that the 3dparty repository > still will be a big mess with hundreds of licenses.
Perhaps you should consider using Composer for (some) this: http://packagist.org/about-composer http://nelm.io/blog/2011/12/composer-part-1-what-why/ It works quite nicely Evert _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
