On Tue, Oct 20, 2009 at 6:25 AM, Chris Withers <[email protected]>wrote:
> > Thomas G. Willis wrote: > > I guess what I would like to have is something like... > > > > c:\project\myegg-src>python setup.py bdist_egg > > > > to produce... > > > > ./myegg-0.0 > > ..../docs > > ..../myegg > > ..../tests > > > > But I'm not quite grokking how to get this to work. > > Why would you want to include docs in an egg? An egg is not designed to > have content read by humans ;-) > > Docs in a sdist, yes, that makes sense and I have the same questions you > do, but bdist_* makes no sense... > > cheers, > > Chris > > Well, I guess I have a fundamental misunderstanding of what bdist means. bdist_rpm makes an rpm, and I've seen rpms that put docs in /usr/share. bdist_wininst makes an install exe, and I've seen installs that put docs somewhere. So, that's why I was thinking it must be possible. But maybe the "unspoken" requirement is that if you want to go that route, put it under your package and list it in the data_files. I looked at the ipython setup.py and , holly crap there's some complex stuff in there but that's exactly what I was hoping to accomplish. I'm just surprised it's not as easy. I never though I'd say this about anything related to python, but, I kind of want ant, just without the xml. Apologies for the noise that has really nothing to do with Sphinx. I'm sure I will have more questions that are more relevant since I'm stepping up my documentation efforts. -- Thomas G. Willis --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en -~----------~----~----~----~------~----~------~--~---
