[Fred] > Ok, here's the plan: Change Setup.in to Setup.dist, and provide a > copy as Setup. Since this doesn't help if the source and build > directories differ, configure.in can be modified to create Setup if > (and only if!) it doesn't exist, by copying it from $srcdir/Modules/. > I have the changes to configure.in, configure, Setup*, and > Modules/Makefile.pre.in ready, but I still need to update the > instructions in the README & possibly elsewhere. > Does this sound agreeable? Sure, except I'm not comfortable with having two files with identical contents under CVS control. How about not checking in Setup, but creating it in configure if it doesn't exist? This is necessary also for the following reason: when you build in a different tree than the source tree, you should get a fresh copy of Setup in the build tree -- another copy of Setup in the source tree is useless. --Guido van Rossum (home page: http://www.python.org/~guido/)
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