The present design with two optional packages gap_packages and database_gap was dictated in the 1st place by copyright issues with their contents, preventing them from being standard.
Since GAP release 4.9, all these issues have been resolved upstream, and I propose these spkgs to be merged into the standard GAP spkg. The upstream GAP tarball already contains everything we install there (and more). With this, Sage's GAP would be much closer to the upstream GAP, and packagers of Sage would be made happier too. As a part of the update to GAP 4.10, I've already merged database_gap into gap spkg on https://trac.sagemath.org/ticket/26856 Unless I hear well-motivated objections (no, don't tell me about big tarballs and increased by 3 minutes build time), I'll proceed with doing the same to gap_packages. Dima -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
