-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convert manual to GAPDoc #9
Comments
You can publish a location from (almost) any place, by placing a symlink to GAP's But if you make a new clone, then yeah, you need to again clone BTW, even with GAPDoc, one has to be very careful if one builds the package outside the GAPROOT, as there is a risk that one ends up with absolute paths in the generated HTML, namely for links to documentation in other packages, if one has any of those. I think we applied various tricks to mitigate that in |
Keeping gapmacro-based manual has some inconveniences when one uses ReleaseTools. First, I can not publish a release from any place, since it has a relative path to gapmacro.tex. Second, symlinking the clone into
gap/pkg
did not help. So I had to make a new clone of the repository. Third, inside that clone I had to recreate gh-pages subdirectory with:With GAPDoc, none of these steps would be needed...
The text was updated successfully, but these errors were encountered: