Phillip J. Eby wrote: > At 10:13 AM 3/16/2006 -0600, Ian Bicking wrote: > >> It occurs to me that maybe it would be easiest to create an RPM that >> includes Paste, PasteDeploy, and PasteScript all together? That would >> simplify all of this, it seems. > > > That would certainly fix the conflict problem in the short term. > > In the long run, I'd like a better solution, though. Separate > components for namespace packages are too good a thing to give up on > without a fight. I'm tempted to see if there isn't a way to create an > import hook in pkg_resources that would allow namespace packages to work > without having an __init__.py. That would eliminate the file conflicts, > albeit at the expense of requiring pkg_resources to be imported before > any namespace packages.
Another solution is at the package level -- RPMs can overwrite each other's files, if they are spec'd out to do that somehow. This is not very clean -- I don't know which if any package is allowed to ultimately delete that file. With some post-install hooks you could just create the file, and delete when there's nothing left in the package. This would have to be handled for every packaging system. But there's only a couple anyone uses. -- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
