I’d say, if the dependency on emailadmin is strong, such as:
If the users get a whole lot of errors on the screen, when there is no
emailadmin, or the
involved functionality is of vital use, then I think adding it, is a good
idea.
If not, dont’t.
Regards
Klaus
I recently updated the workflow dependencies, but may have gotten them
wrong.
Régis, I noticed you mentioned a few months ago that you currently use
workflow on an old 1.2 platform. Should I have left 1.2 in?
Also, it appears that workflow has an unmentioned dependency on
emailadmin (because of the bo_agent_mail_smtp).
Should I make that dependency explicit, or try and remove the
dependency?
This SF.Net email is sponsored by the Moblin Your Move Developer’s
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers
–
Stylite GmbH
[ open style of IT ]
Morschheimer Strasse 15
D - 67292 Kirchheimbolanden
fon 06352 . 70629-0
fax 06352 . 70629-30
email kl@stylite.de
www.stylite.de
Geschäftsführer: Nigel John Vickers, Andre Keller
Registergericht Kaiserslautern, HRB 12087
This SF.Net email is sponsored by the Moblin Your Move Developer’s challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers
