Hey Tom,
actually I wrote a proposal about dependencies of apps (mainly apps
depending on other apps) to this mailing list on 8th of april, hoping to
start a constructive discussion about it...
I thought about something like this:
<info>
<!-- app info -->
<requires id="required_app">
<!-- to define specific versions of required_app, optional -->
<min>0.2</min> <!-- optional -->
<max>0.5</max> <!-- optional -->
<version>0.15</version> <!-- a specific version; optional -->
<version>0.16</version> <!-- optional -->
</requires>
<requires id="another_app" />
<conflicts id="evil_app">
<max>0.3</max> <!-- same version properties as above -->
</conflicts>
<!-- ... -->
</info>
But we could make this even possible for PHP libraries etc.
Cheers
Florian
Am 18.04.2012 23:17, schrieb Tom Needham:
Hi All,
Had an idea of how to implement requirements when installing apps. For
example, when the gallery is installed, it need to check if gd is
installed, rather than just giving an error. So I though about adding a
<requirements> section to the apps info.xml. In there we can list
<functions> <classes> and <extensions> that we can check exists when
enabling the app.
We can also do a check when we do the overall owncloud install to check
that the default enabled apps have all their requirements met.
What do you think, is this flexible enough for apps?
Thanks,
Tom
Tom Needham
[email protected] <mailto:[email protected]>
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
--
Florian Hülsmann
<[email protected]>
http://cbix.de
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
