-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
Add experimental gap3_jm package #20107
Comments
comment:1
How do I actually find all binaries? Such as
Are any of these okay to keep, such as the dvi files? |
Replying to @stumpc5:
I think this is the problem: it doesn't seem to be the "official" GAP3 package, just some random repackaging of GAP3. |
comment:3
Replying to @jdemeyer:
The development of GAP3 has stopped a long time ago. But there are several GAP3 packages that have never been ported to GAP4, and which are still developed. From that webpage:
So this is the only place where we can find up-to-date versions of the GAP3 package chevie to work with unitary reflection groups and their representation theory. I fail to see what might be wrong with adding support for those packages using that "random repackaging" since I and several others need them. I install the packages myself and then use them from within Sage, but since several things inside Sage are about to depend on that package - see #11187, #11010, #10819 - I think it is worth providing the option for others to automatically install that version of GAP3 with the newest chevie package. |
comment:4
Replying to @stumpc5:
All the above doesn't explain why you use the repackaged version and not the official GAP 3 release from http://www.gap-system.org/Gap3/Download3/download.html
No, the official
Because the repackaging seems to made in a messy way, see #19164. |
comment:5
Frank Lübeck's page How to get CHEVIE also says to download the official GAP3 release and doesn't talk about the "repackaged" version. |
comment:6
Replying to @jdemeyer:
Neither this nor the above is up-to-date. Afaik, Jean Michel is the only person still actively developing chevie and his website is the only place where these new versions can be found. E.g., I found a small bug in chevie last month (so years after the release of Using any other version of gap3 and chevie will result in running into old mistakes that will slow down my understanding of research problems I compute! |
comment:7
With "new version", I guess you mean a new version of the repackaged GAP3? It should be possible to just get the up-to-date chevie sources without all the extra clutter. |
comment:8
From my email discussion with Jean Michel:
@jdemeyer, what do you think how to proceed from here? |
comment:9
First of all, thanks for the clarifications! I think that somebody (either Jean Michel himself or somebody on this Sage ticket) needs to package a source-only repackaged GAP3. Further questions to be asked to Jean Michel:
|
This comment has been minimized.
This comment has been minimized.
comment:11
Replying to @jdemeyer:
I don't understand how this differs from my initial suggestion on this ticket. |
comment:12
Replying to @stumpc5:
It does not differ. It's just that the situation has been clarified, making sure that your initial suggestion is the right thing to do. |
This comment has been minimized.
This comment has been minimized.
comment:14
Dear Christian, Further questions to be asked to Jean Michel:
OK, I will try to be clear on my webpages. The fact is I do not distribute
I could try if I understand exactly what this means. But this should
Yes. |
This comment has been minimized.
This comment has been minimized.
comment:16
Replying to @stumpc5:
It means: delete all binaries (i.e. system-specific) from the package. Make sure that the package has a build system such that it can be built/installed in a standard Unix environment.
Well, I wouldn't call it a "for-Sage distribution". Call it a "source distribution". The actual filename doesn't matter much, most likely we will rename it for Sage anyway. |
comment:17
Replying to @jdemeyer:
I will try to do that. |
comment:18
Also (this is mostly a comment for Jean Michel): ideally the binary distribution would be made from the source distribution, not the other way around. |
Branch: u/stumpc5/20107 |
comment:20
I prepared a first version by
@jdemeyer and @tscrim: I would very much appreciate if you could have a look! If the linked tarball is okay, I would discuss with Jean Michel whether he could provide such a source distribution directly on his website. New commits:
|
Commit: |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:23
This is far from an exhaustive list: +if [[ $UNAME == 'Linux' ]]; then
+ if [[ $(uname -m) == 'x86_64' ]]; then
+ MAKE_COMMAND='x86linux-gcc64'
+ else
+ MAKE_COMMAND='x86linux-gcc'
+ fi;
+elif [[ $UNAME == 'Darwin' ]]; then
+ MAKE_COMMAND='macosx-gcc'
+fi Is gap3 only supported on those architectures? In that case, it will need to be an experimental package. |
comment:24
You should check for errors in |
comment:126
Replying to @dimpase:
Jean, it is okay to comment out the lines
in Otherwise, I could also try to build those packages that needs compilation, but already |
comment:127
You can comment out all of them but arep.g Generally speaking, arep has some functionality which does not need its binaries. You could delete the subdirectories bin and src of arep if you keep the rest. In the version I am preparing (complete gap3 distribution), I will make sure all included packages can be compiled |
comment:128
Of course. They do not deal at all with the operations records which is the crux of the matter. |
comment:130
Dima, thanks for checking! I deleted all packages that need compilation. This solved your request on this behalf. I would appreciate if you could retry to build it on OSX (don't forget to download the new tarball first); at least the two broken symlinks
are now gone together with the complete package. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:132
it does not fly on OSX:
|
Changed branch from u/stumpc5/20107 to public/20107 |
comment:133
The reason for this must be that the flag New commits:
|
comment:134
also, is this meant to fail:
|
comment:135
Replying to @dimpase: Thanks for rechecking and for fixing the make target for osx!
I doubt this worked before, I only replaced
Getting this properly working will be part of our finally-get-reflection-groups-smoothly-in-sage-days next week. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Reviewer: Jeroen Demeyer, Dima Pasechnik |
comment:138
Many thanks to both of you for your reviewing work on this ticket! |
comment:139
Replying to @stumpc5:
Exactly. This ticket is not about fixing all doctests, just about adding the package. |
Changed branch from public/20107 to |
Changed commit from |
comment:141
|
We have been trying to have an optional GAP3 package for a while now. Instead of the official GAP3, we instead use a forked package gap3_jm which has regularly been updated.
Previously, this was made a Sage package (#8906) but it contained binaries, so it was removed again (#19164).
I removed all binaries, and prepared a new tarball at http://downloads.findstat.org/gap3-jm5-2015-02-01.tar.gz .
CC: @saliola @tscrim @sagetrac-jmichel @simon-king-jena
Component: packages: experimental
Keywords: gap3, experimental package
Author: Christian Stump
Branch:
a0d0e18
Reviewer: Jeroen Demeyer, Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/20107
The text was updated successfully, but these errors were encountered: