Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
... when asking for printed output, since `~/.gap/gaprc` may contain `Print` statements.
- Loading branch information
... when asking for printed output, since `~/.gap/gaprc` may contain `Print` statements.
7237970
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ThomasBreuer and @fingolfin.
I've just discovered this while debugging the package manager. The
-r
flag means that a GAPDoc installation in~/.gap/pkg/
is not sufficient, and that we need to have GAPDoc installed in the GAP root in order to compile any other packages. Obviously it'd be good if the user pkg directory could be used.Is there a way we could remove the
-r
here without breaking things?7237970
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about instead setting
GAP
before startingBuildPackages.sh
so that it gives a suitable-l "PATH/TO/YOUR/GAPROOT;"
so that it definitely sees "your" GAPDoc first?7237970
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the suggestion. I've had a go, but I'm struggling a bit. If I call
inside the directory of the io package, I get
Maybe I'm using
-l
or--with-gap
wrongly? If I specifyGAP=...
at the beginning of the command, it seems to be ignored.