2008/9/28 Ian Bicking <ianb@colorstudy.com>
Greg Ewing wrote:
Phillip J. Eby wrote:

the domain knowledge embedded in the distutils are of fairly limited scope and kind:

* Extension building, compile/link options and defines
* Wildly-differing installation path schemes across platforms
* Platform distribution formats like bdist_rpm, bdist_wininst, and bdist_msi

Seems to me that if there were a well-defined API for
plugging in platform-dependent modules, it shouldn't be
too hard to find people willing to contribute modules
for the platforms they're familiar with.

For the most part I don't think you'd even need plugins, these platform-dependent tools could just be independent, maybe working more like:

 make_wininst SomePackage/

They'd read the metadata about the package, and just do their work however they wanted.  Plugins get complicated compared to stand-alone tools.


+1

this is exactly the same thing for uploading or registering a package at PyPI. We don't need to use command plugins for that as long as
the medata can be read to do the job.


 



--
Ian Bicking : ianb@colorstudy.com : http://blog.ianbicking.org
_______________________________________________



--
Tarek Ziadé - Directeur Technique
INGENIWEB (TM) - SAS 50000 Euros - RC B 438 725 632
Bureaux de la Colline - 1 rue Royale - Bâtiment D - 9ème étage
92210 Saint Cloud - France
Phone : 01.78.15.24.00 / Fax : 01 46 02 44 04
http://www.ingeniweb.com - une société du groupe Alter Way