"Fred L. Drake, Jr." <fdrake at acm.org> writes: > Michael Hudson writes: > > One thing that puzzled me: Doc/Makefile seems to require that > > Doc/tools is on $PATH, unless I'm misunderstanding something. > > It definately doesn't require that; I've never used Doc/tools/ on > $PATH. One thing it was requiring (only recently) was that there was > a mkhowto symlink somewhere on the $PATH that pointed to the mkhowto > script. > > I've removed that constraint for the trunk. > > The intention is that we should be able to use a mkhowto script from a > different checkout; you can still modify the MKHOWTO make variable to > do that, but it's not so valuable on the trunk as on the maintenance > branches (where we want to use mkhowto from the trunk). Do we? Why? Thomas
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