2009/12/9 Bruce Momjian <bruce@momjian.us>:
> I frankly think the patch should be thought of as the SE-Linux-specific
> directory files, which KaiGai can maintain, and the other parts, which I
> think I can handle.
I think that's a horribly bad idea.
We have already got a similar issue with ECPG, which clearly stagnates
whenever Michael is busy and don't have time to go through the
patches. Because it's "his code", and nobody else knows how to and/or
cares to maintain it. And this is just a single piece of the frontend
that doesn't affect anything else.
If you want to do something similar for sepg, then sepg needs to be
turned into a full plugin system, where the plugin is a completely
separate thing. In which case the plugin can be developed separately,
for example on pgfoundry (and be considered to merge later, if we
want, but not necessarily ever since it has a narrow user base).
I haven't looked at the patch properly for quite a while, but I
imagine turning it into such a plugin is not feasible. Because if it
is, why haven't this been done already? :) But if it is, perhaps that
is something we should consider, since it lessens the maintenance
burden into "just" the API (which is still a huge burden compared to
many of our APIs, but it is a lot less than what the patch is now)
-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/
