> I don't know much about modules, but would this allow Jack to check > out the main code and the MacPython code into a single work > directory (which he needs)? Using CVS modules allows to merge parts of the tree into a single sandbox. E.g. you could do macpython python/dist/src &Mac 'cvs co macpython' then would give you a dist/src directory, which also contains a Mac directory (where Mac is another module, alongside with /python, or a CVSROOT/modules entry). You could use an exclude list, e.g. macpython !PC !PCbuild !RISCOS python/dist/src &Mac What you *cannot* do is to merge modules on a per-directory basis; all files in a single directory must come from the same CVS module - you can think of ampersand modules similar to Unix mount(1)ed file systems. 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