Closed sheerluck closed 2 years ago
I think an update for this has just been pushed. That could be the opportunity to do some more work on this. The whole meataxe thing is quite ugly. I am concerned that you must have executed that as 'root' and that this would need to be post-merge. If it doesn't depend on the architecture, the files could be generated once and shipped as a separate tarball. Otherwise we have to control where the output will land.
It is very much doing the post-install from sage. https://github.com/vbraun/sage/blob/develop/build/pkgs/meataxe/spkg-postinst.in - it looks like I can control where things go so it should be good.
I have pushed a 1.0.1-r1 ebuild which should install everything that is needed. Can you test and check it is behaving as you expect.
I tested it and problem is solved.
I noticed that in the last two versions of sage in the overlay, I dropped building options for meataxe and bliss bindings. This was not on purpose and will be restored in 9.7. I'll note that building against the latest bliss seems broken so it may need a dependency tweak.
According to https://github.com/archlinux/svntogit-community/blob/packages/shared_meataxe/trunk/PKGBUILD we need
When I did that in
/usr/share/meataxe
I getand only after that I was able to
sage: M = MatrixSpace(GF(25, "z"), 2, 3)([1, 2, 3, 4, 5, 6])
fromsrc/sage/matrix/matrix_gfpn_dense.pyx
and finally