On May 11, 2011, at 12:45 PM, Stefan Kaltenbrunner wrote:
> yeah and now the fun starts... "ok we use the packaged postgresql - in need plperl in ther to be 5.12", "we cannot
usethe packaged DBD::Pg because that one needs to be compiled agains 5.12 as well", "an oh because it is simpled we
cannotuse any packaged perl lib at all because it is so much easier if I just install my own copy that will never be
securitytracked".
> We(mostly magnus) basically spent man years to get the new infrastructure up and long term maintainable and having to
startsupporting random hand compiled complex packages (again) on them does not sound like the right thing to do - it is
wherewe came from and we defintely dont want to get back there.
> If it really needs perl 5.12 (and maybe other stuff) I would rather think it is better to keep pgxn as a seperate
entityfor the time being.
> Infrastructure is all about reliability, sustainability and manageability - that often does not mix too well with
developerneeds but that is how it is...
Yeah, I don't want to create maintenance nightmares for you guys. That's why I said I'm happy to manage it myself.
I don't think it *has* to use Perl 5.12; I could do the work to backport it, I don't think it'd be a ton of work,
mostlyjust an annoyance. I'd strongly prefer 5.12, obviously, but if it's just not do-able, and you don't want me
buildingstuff separate from the Debian-packaged stuff, I could make it work.
There almost certainly will be some CPAN modules I use not packaged, though.
Best,
David