On Tue, 25 Feb 2014 21:32:32 +0100, nap <napar...@gmail.com> wrote: > On Tue, Feb 25, 2014 at 4:59 PM, Rémi Palancher wrote: > There has been many discussions on IRC channel lately and some > commits > about the setup.py in order to fix some bugs regarding pip and also > complains about its inner complexity. > > yep, it's over complex for an easy task indeed.
Cool, we all agree that setup.py is too complex! > As a packager I think I understand your thoughts, but one important > point is that we should be not rely only on the packages only. As we > are going quite quickly on the features, we should also be able to > run > in a "quite a good" way with upstream. The fact that I personnaly run > my servers in this mode can make me not so objective of course :) For particular early adopters or developer needs, it is not very hard to set up infrastructure to automatically build upstream rpm/deb/whatever packages at every commits or every nights. For that particular users, using last features would as simple as updating distribution packages. > One last important point is that the setup.py should be still usable > to build a package in a good way, and currently the setup.py is just > too complex to handle new files or filterings (like no init.d files > option or thing like this). We will have to rewrite it for the 2.2 > version, and this time I hope it will automatically make it possible > to run with pip :) OK but I can't get how you intend to significantly simplify the current setup.py logic _without_ removing all the included magical features. What's the plan? -- 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
