Ian Bicking wrote: >>>Eggs give room for package metadata that doesn't exist otherwise. >>>Putting dependencies aside, this is functionality that simply doesn't >>>exist with the standard distutils installation. <snip>
>> Understood, but wouldn't it be reasonably possible to >> also install this meta-data into a standard site-packages >> package directory ? <snip> > An egg and Python packages don't map 1-to-1. An egg can contain > multiple packages (which is fairly uncommon so far), but also a > top-level package can exist in more than one egg (i.e., namespace > packages, like zope.interfaces or paste.script). The metadata belongs > to the egg, not to the package inside the egg. I'd like to bring focus back to immediate problem at hand (and yes, I understand there is something much bigger involved). The ultimate goal is to debianize TurboGears, reading the above, and other posts using the legacy site-packages (non-egg) installation will "break" TurboGears? -- Bob Tanner <[EMAIL PROTECTED]> | Phone : (952)943-8700 http://www.real-time.com, Minnesota, Linux | Fax : (952)943-8500 Key fingerprint = AB15 0BDF BCDE 4369 5B42 1973 7CF1 A709 2CC1 B288 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
