On Fri, 28 Feb 2014 02:56:01 +0100, David DURIEUX <d.duri...@siprossii.com> wrote: > Hello, > > with the real complexity of setup.py, I have rewriten it few hours > ago > and commited it in repository.
I have to admit I find quite weird and confusing you have rewritten from scratch a new setup.py and pushed it on master branch during RC freeze without even noticing package maintainers. Needless to say I feel a bit worried. Maybe you are an incredible genius and you have developed a both simple and fully-featured script everybody will embrace, but I seriously doubt that. Can you briefly explain what were your design goals? Is your script strictly compatible with the previous one? Are there known regressions? What are the planed evolutions? Can we at least determine here (together!) on some points regarding this setup.py: - what the script should/shoudn't do? - what the package maintainers should manager himself/herself? - how distributed setups are handled? - documentation packaging? Can we discuss about this? It shouldn't be hard to agree on these points. At the end, hopefuly both upstream developers and package maintainers will clearly understand what's their job and how to not bother others job. -- Rémi Palancher http://rezib.org ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ Shinken-devel mailing list Shinken-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shinken-devel
