| ../irclogs/#mantishelp.2009-12-09.log | ||
| --- scribe started --- | 00:00 | |
| dirtyal | I've upgraded to the last git, 1.3dev and the dource integration stopped working | 15:51 |
|---|---|---|
| dirtyal | I am getting the error: Invalid repository name | 15:51 |
| dirtyal | any ideas? | 15:51 |
| dirtyal | has anyone have problems with 1.3 and source integration | 16:06 |
| dirtyal | ? | 16:06 |
| dirtyal | nuclear_eclipse: are tou there? | 17:08 |
| g0rd0n_ | hmm found out i had to modify core/ldap_api.php to change the "mail" field to "email" in order to get the adresses from ldap... maybe the ldap fields should be configurable in the config file? | 18:34 |
| g0rd0n_ | oh well, i will patch the ldap_api.php anyway to set user level based on the ldap group field :P | 18:38 |
| dirtyal | I am having a problema with the source integratoin | 18:38 |
| dirtyal | the PHP, when running svn | 18:39 |
| dirtyal | set the apache home to / | 18:39 |
| dirtyal | so SVN tries to read the .subversion inside the root directory | 18:39 |
| * paul__ needs more time | 18:44 | |
| g0rd0n_ | / ? | 18:50 |
| paul__ | life :) | 18:50 |
| giallu | nuclear_eclipse, there? | 22:57 |
| nuclear_eclipse | hi giallu | 23:05 |
| giallu | hi | 23:05 |
| giallu | is there a way fora plugin to require an existing function/class/extension ? | 23:05 |
| nuclear_eclipse | what do you mean? | 23:06 |
| nuclear_eclipse | example? | 23:06 |
| giallu | I mean how it should be best to handle the situation: plugin X requires php-xml, but php-xml is not installed | 23:06 |
| nuclear_eclipse | hmm | 23:07 |
| nuclear_eclipse | well, the plugin's main classfile could check for the extension, and only declare the class if found? I dunno | 23:08 |
| giallu | what about extending the plugin_dependency function to handle this? | 23:09 |
| giallu | it would catch it at installation, IMHO the proper place | 23:09 |
| nuclear_eclipse | yeah | 23:09 |
| paul__ | what's php-xml | 23:09 |
| giallu | paul__, an example | 23:09 |
| paul__ | :P | 23:09 |
| giallu | so let's see... | 23:10 |
| nuclear_eclipse | I could see adding an ->extensions property that lists a set of php extensions needed, and checking those similar to normal plugin dependencies | 23:10 |
| paul__ | strikes me as somehting for a function within the plugin to do | 23:10 |
| paul__ | a pre-install type function | 23:10 |
| nuclear_eclipse | well, the benefit of having the core do it would be that the manage plugins page could list the missing dependencies the same way it does for plugin requirements | 23:11 |
| paul__ | then we get to deal with stuff like | 23:11 |
| nuclear_eclipse | but yes, the plugin could do this itself already | 23:11 |
| paul__ | what if a plugin requires xdebug 2.5 as opposed to xdebug 2.0 for example | 23:11 |
| paul__ | a check for 'xdebug' would return true in both cases | 23:11 |
| giallu | ok. so you both see a better fit to add a "pre_install_check()" kind of method to plugins? | 23:14 |
| nuclear_eclipse | well, that's already there | 23:14 |
| * giallu looks | 23:14 | |
| nuclear_eclipse | a plugin's ->install() method can return false to fail installation | 23:14 |
| paul__ | what it should be possible to do though is have the pre_install_check populate the missing dependencies bit with information | 23:14 |
| paul__ | so for example, if you had a video encoding plugin for mantis, you could check if the shell has ffmpeg on it, and if it doens't tell the end user for example | 23:14 |
| paul__ | nuclear_eclipse: I like your idea! | 23:14 |
| nuclear_eclipse | would be nice if php had a function for checking the version of installed extensions... | 23:14 |
| paul__ | yea | 23:15 |
| giallu | ok, so I overload the install() function and add my checks | 23:16 |
| nuclear_eclipse | yep | 23:17 |
| giallu | no docs there, I could hardly tell that was the right thing to use :( | 23:17 |
| * giallu checking docbook | 23:18 | |
| nuclear_eclipse | yeah, docbook is still way behind the implementation =\ | 23:18 |
| nuclear_eclipse | I added a lot of documentation to the "how to make a plugin" part last week, just need to finish that and document the actual specifics of the plugin interface | 23:21 |
| giallu | tbh, I'd exptected some doc _in_ the MantisPlugin.class.php file | 23:21 |
| * giallu adding some | 23:21 | |
| nuclear_eclipse | thanks :) | 23:23 |
| nuclear_eclipse | the code *is* the documentation ;) | 23:24 |
| paul__ | didn't we add some already? ;/ | 23:24 |
| giallu | nuclear_eclipse, how do I go about adding errors messages on the failed install? | 23:51 |
| * giallu is sorry for being clueless | 23:51 | |
Generated by irclog2html.py