Yeah and dependancy checker use an hard-coded list... and is not really possible to extend... we may want to add a collback or a parameter to let the app register the dependancy...
On Tue, Aug 21, 2012 at 1:47 PM, Marcos Mezo <[email protected]> wrote: > On 21/08/12 12:45, Christian Reiner wrote: >>> >>> On Sunday 19 August 2012 19:42:17 you wrote: >>> just to add little more things to the discution, >>> it would be great if there were also a requirement checker about other >>> things like php modules, or even plateform ... >> >> To me it sounds like these checks should be requested as a part of the >> install >> >> or upgrade routines. That is where the environment owncloud is meant to be >> installed into should be checked. >> >> This discussion was about the check blocking or enabling single apps >> inside an >> existing owncloud installation. Though certainly possible I doubt adding >> such >> checks at this point brings any advantage. Such basic aspects must be >> checked >> and fulfilled to get owncloud running anyway. Is there any benefit if >> these >> aspects are checked again and again, each time an app is installed or >> enabled? > > If I am correct not every module is necessary for every installation. In > fact if I remember well, the PHP Curl extension is not needed for a basic > owncloud installation, but the bookmarks application uses it. > > By the way, I found out about that in the admin menu. After activating the > "dependency status" application, on the main amin screen you can find which > modules are needed and which application is using them. I had the curl one > in red, saying that bookmarks needed it. > > So I gess it's ok to check dependencies on every app > installation/activation. > > Marcos > > _______________________________________________ > Owncloud mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/owncloud _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
