On Jan 12, 2008, at 11:05 AM, Charles Lepple wrote: > On Jan 7, 2008 10:57 AM, Jed Frechette <[EMAIL PROTECTED]> wrote: >> I was wondering if there was a reason why docutils gets installed to >> %p/lib/docutils/ rather than site-packages? > > Jed, > > Brendan Cully and I talked about this about a year and a half ago, but > essentially it is the way it is because at the time, the docutils > utilities were the only tools using the interfaces in %p/lib/docutils. > To package it properly would require creating -py* splitoffs for each > of the various Python versions in Fink. (Because each Python major > version uses different bytecode formats, packages like should be > installed in version-specific site-packages directories.) > > With the Fink info file variant syntax, this should be simpler. I will > try to take a look at that later this weekend.
Thanks for looking at this, I knew there was probably some good reason. I asked because I'm trying to package some of the Enthought tools and their documentation generator Endo [1] tries to import docutils. I also noticed that some of their scripts expect the rst2* scripts to exist without the .py extension. I'm not sure how other distros handle this but at least on my Debian box these scripts are installed without the extension. Best, [1] https://svn.enthought.com/enthought/wiki/EndoHowTo -- Jed Frechette University of New Mexico Lidar Lab www.unm.edu/~lidar ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
