[Slackbuilds-users] trying to fix sage-8.1 build script - advice needed
jebrhansen+SBo at gmail.com
Mon Jan 8 04:41:43 UTC 2018
On Sun, Jan 7, 2018, 11:16 PM King Beowulf <kingbeowulf at gmail.com> wrote:
> On 01/07/2018 05:55 PM, David Melik wrote:
> > On Sun, 07 Jan 2018 14:13:07 -0800, King Beowulf wrote:
> >> I'm attempting to upgrade and fix a few issue with the sage build.
> >> However, upstream seems to think that no one wants to compile a
> >> redistributable install package.
> >> If anyone has any ideas, let me know.
> >> -Ed
> > SAGE really has many issues, and I'd still like to use it, but am
> > skeptical whether it's worth anyone making a SlackBuild until the SAGE
> > programmers take most users into consideration.
> I'm glad I'm not the only one who thinks upstream has been drinking the
> wrong cool-aid. 'forking' 'rump' holes....
> Compiling and packaging worked before with a bit of gyration, but
> upstream changed somnthing, especially with this non-root compile fetish
> of theirs. Now, in the the prebuilt binaries, they have a python script
> that will patch all the dozens of hard coded files:
> p = SearchAndReplace(ROOT_PATH,
> Maybe I have to just set SAGEROOT to /tmp/SBo/sage-8.1BLAHBLABLAH.... to
> match the number of bytes they use so that the script won't crash.
> Or extact and compile in '/opt/sage' and create a package there then
> delete, but that might upset some of our more sensitive and pedantic
I don't really have much experience with this (and don't use sage at all),
but could you set up the directories as needed under /tmp/SBo/package-sage/
and then just chroot it? Maybe with a bind mount for the needed system
directories (assuming it doesn't need the whole system, since that'd be a
little excessive to bind mount)? That way, once the bind mounts are
removed, the directory can be packaged up as normal.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SlackBuilds-users