Setting up the development environment for Semigroups.

[JosephDayngerRuiz]

What was the process again for getting the development environment for semigroups? Willing to go over it before Wednesday's meeting too. I recall being able to use the package manager to get a copy of this repository with libsemigroups so that when I use git in that repository it has the correct version of libsemigroups with its files ignored in git and I can use it as an up-to-date fork of semigroups. I may answer my own question before the Wednesday meeting and if I do, I will post a step-by-step process of how to set up the development environment.

[JosephDayngerRuiz]

Here is my work around:
The package manager in gap can install a package from a github website link followed by .git
InstallPackage("https://github.com/semigroups/Semigroups.git")
However, this seems to always install into .gap/pkg/Semigroups. Inside this directory is a weird error I found and I want to investigate it later, so before installing the new package I renamed the folder currently inside .gap/pkg/Semigroups to .gap/pkg/Semigroups-weird-error-version-5.6.1.
However, even after renaming the folder and running the installation command I got

gap> InstallPackage("https://github.com/semigroups/Semigroups.git");
Package "Semigroups" already installed via git. Update it? [y/N] 

I am unsure if answering "y" will cause it to find the renamed folder and overwrite what is there.

[JosephDayngerRuiz]

Well I answered "N" and I assumed that would abort the installation and now it is cloning to .gap/pkg/Semigroups.

[JosephDayngerRuiz]

I opened the folder .gap/pkg/Semigroups in VScode and did a git diff and there seem to be no difference between remote and the local version. I can continue from here.

[JosephDayngerRuiz]

One downside is this set up no longer is associated with the fork of semigroups I have on github. My plan is to delete the github fork and somehow associate the local fork of semigroups to the open pull request I have for generalized conjugacy classes.

[JosephDayngerRuiz]

This did not solve the problem. I then changed the name of every folder with semigroups in the name to have a prefix "no-". Doing this forced the brand-new installation to be used.