Joe Atzberger <[email protected]> wrote: > [...] I don't care if Steve Jobs himself built the systems, Koha > does not have the choice to "accommodate" miscompiled dependencies. Any > hack around we make would not be maintainable. [...]
The Koha project had the choice not to adopt the problematic feature so late in 3.0 and it would have been as maintainable as Koha had been for years - Koha has been working around everything from shell inconsistencies upwards for years. > But since the author was gracious enough to tweak H:T:P for your case, > where's the cause for a fork now? As I wrote to Joshua at LibLime in private about 30 mins before your email, the only reason the fork remains now is that my co-op has no available resources to merge it back in yet. > [...] Koha developers have spent many > hours investigating your problem and specifically determining the cause, for > absolutely no reward and no payoff to Koha. Not even a pro forma "thanks". Yes, some were helpful. I definitely thanked most of them by IRC and private email. Sorry if anyone felt missed out, but I don't like personal emails like the above being sent to mailing lists, so I'll cut the rest of this short: we can't report further upstream because of annoying commercial reasons (not like we're the only Koha company ever to get into that sort of problem), we've explained the fork reasons, the git tree is public (give or take occasional server problems) and we should be taken seriously because we've been around a long time, we're so open and honest it hurts and we'll return to the mainline once we can fund it. Regards, -- MJ Ray (slef). LMS developer and supporter for a small, friendly worker cooperative http://www.ttllp.co.uk/ http://mjr.towers.org.uk/ (Notice http://mjr.towers.org.uk/email.html) tel:+44-844-4437-237 _______________________________________________ Koha-patches mailing list [email protected] http://lists.koha.org/mailman/listinfo/koha-patches
