> I have mixed feelings. There are really two things that we could > do: We could add Expat to our CVS repository, which means syncing a > bunch of files everytime a new Expat release comes out, or we could > bundle the Expat sources with the Python source distribution when the > distribution is built, but not add them to CVS. This avoids the extra > files in CVS, but complicates construction of the distribution and > adds a new wrinkle to the configuration management. I'm in favour of putting it into the CVS. This will allow CVS users to build it, and it will allow proper integration and testing of required changes into setup.py (and Setup.dist; the current text has caused a lot of confusion in the past). Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4