On Dec 2, 2007 8:33 AM, Ian Docherty <[EMAIL PROTECTED]> wrote: > Zbigniew Lukasiak wrote: > > On Dec 2, 2007 12:38 PM, Ian Docherty <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> > wrote: > > > Zbyszek > You have to remember that Siemens are responsible for ensuring the > stability of the public facing infrastructure. > This makes it important not to introduce new modules, or upgrade > existing modules, without an extensive > testing period to make sure it works with all existing applications. The > trouble with this is that it is easier to > keep stable (or work around existing known problems) by not installing > anything new. > > > Sure - but as I understand BBC is their client and this policy makes > the life of BBC programmers pretty miserable. > > > Yes, it does make for a pretty frustrating work environment sometimes and > although Siemens should > be working for the BBC it often feels like the other way around. >
Seems poorly thought out. It isn't as if you can't specify module search paths on a per application/profile/platform basis. If a project needs modules, why can't it have its own whitelist? I'd go absolutely nuts with this :) Your patience much be immense.
_______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ Dev site: http://dev.catalyst.perl.org/
