Fredrik Kuivinen [off-list ref] writes:
Not supporting one of the major Linux distributions isn't ideal
though, so maybe we should do something about this. I will have a look
at rewriting the code to not use subprocess.
Thanks -- I personally feel that it would be best to just let FC
catch up, solving this problem for us, while you spend your time
on other things first.
Peter, if you feel strongly about it I'd do 0.99.7.1 removing
the 'requires python >=2.4', but as Fredrik says the only thing
that uses Python 2.4 is his recursive merge, and it is not
something we use without the user explicitly asking for it. We
can consider it as the same status as send-email or archimport
which cannot work without Perl modules necessary for their
operation, so if you can install bypassing requires- check that
would work equally well.
Junio C Hamano wrote:
Fredrik Kuivinen [off-list ref] writes:
quoted
Not supporting one of the major Linux distributions isn't ideal
though, so maybe we should do something about this. I will have a look
at rewriting the code to not use subprocess.
Thanks -- I personally feel that it would be best to just let FC
catch up, solving this problem for us, while you spend your time
on other things first.
The problem isn't FC, the problem is RHEL, generally used on machines
for which an OS update it's huge deal.
Peter, if you feel strongly about it I'd do 0.99.7.1 removing
the 'requires python >=2.4', but as Fredrik says the only thing
that uses Python 2.4 is his recursive merge, and it is not
something we use without the user explicitly asking for it. We
can consider it as the same status as send-email or archimport
which cannot work without Perl modules necessary for their
operation, so if you can install bypassing requires- check that
would work equally well.
My suggestion would be to fork off the recursive merge into a separate
binary package which can have the python >= 2.4 requirement (unless
Fredrik just fixes it.)
-hpa