<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>The "I bundled a renamed copy of six" is a totally different case which would not invoke provides-dist. "I merged sqlalchemy with a previously separate but wildly popular declarative / database support / whatever extension" would invoke provides-dist.<br><br>Daniel Holth</div><div><br>On Nov 19, 2012, at 7:41 PM, Donald Stufft <<a href="mailto:donald.stufft@gmail.com">donald.stufft@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<div><span style="color: rgb(160, 160, 168); ">On Monday, November 19, 2012 at 7:37 PM, PJ Eby wrote:</span></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>Can we maybe kill Provides-Dist and its associated baggage first, though?</div></div></div></span></blockquote><div>I would love to kill Provides-Dist. The biggest question there is how do you handle it's</div><div>functionality? If someone needs setuptools but they have distribute installed they</div><div>both shouldn't get installed.</div><div><br></div><div>The need for it for the "2 packages being distributed together" I'm (personally)</div><div>less concerned about since with proper dependency data we should be</div><div>able to just depend on things instead of bundling them. </div>
</div></blockquote></body></html>