On Mon, 17 Jan 2011 09:21:56 +0100 Michael scherer <m...@zarb.org> wrote: > > There is also the issue on bytecompilation ( > https://qa.mandriva.com/show_bug.cgi?id=50484 ). > I have exposed there the various problem, and apart from explaining > that the solution I chosed was not better than the other, no one gave a > compeling > argument into one or the others alternatives.
That depends how "compelling" you expect the argument to be :) The current situation is clearly not satisfactory. The solution of generating bytecode at install time looks fine. I am not an RPM specialist though, but if you have non-RPM specific questions feel free to ask them, I'd be glad to answer. > Finally, a vast part of the policy is handling 2to3, a topic that we didn't > discuss > at all, and I would not be confortable to adopt it without first looking at > it and > discussing it. What is the issue with "handling 2to3"? It's a developer tool and certainly shouldn't be invoked at install time if that's what you are asking. Generally, I don't think you (as a packager) have to invoke 2to3 manually at all. If 2to3 is part of the packaged software's build process, then their setup.py will probably invoke it automatically with the right options. Regards Antoine.
