[Slackbuilds-users] sage up for grabs UNMAINTAINED

[King Beowulf]

All

Anyone who wants to maintain SAGE can have it. I've tried to get a new
version working for months.

1. Upstream does not want you to compile as root
2. All modules paths are hard coded during compile
3. relocatable package impossible? - I can't get it to work

The devs want the end user to compile as user in $HOME, and so seem
hostile to the idea that anyone might not. There are scripts etc to try
to fix the directory paths to relocate the folder tree - they use one
for the bre-built binary - but I can't get it to work, or generate one
for Slackware

I give up. I'm dropping this turd.

Admins,
Please remove my name/email from sage.info and mark as UNMAINTAINED.
I'm tired of getting (hate)emails.

Thanks
Ed

[Glenn Becker]

Thanks for your work on this. I know that thing well enough to know it is a
#$)*@#$@^T& behemoth.

<Loading Image...>

Post by King Beowulf
All
Anyone who wants to maintain SAGE can have it. I've tried to get a new
version working for months.
1. Upstream does not want you to compile as root
2. All modules paths are hard coded during compile
3. relocatable package impossible? - I can't get it to work
The devs want the end user to compile as user in $HOME, and so seem
hostile to the idea that anyone might not. There are scripts etc to try
to fix the directory paths to relocate the folder tree - they use one
for the bre-built binary - but I can't get it to work, or generate one
for Slackware
I give up. I'm dropping this turd.
Admins,
Please remove my name/email from sage.info and mark as UNMAINTAINED.
I'm tired of getting (hate)emails.
Thanks
Ed
_______________________________________________
SlackBuilds-users mailing list
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Fellype do Nascimento]

Post by King Beowulf
1. Upstream does not want you to compile as root
2. All modules paths are hard coded during compile
3. relocatable package impossible? - I can't get it to work
The devs want the end user to compile as user in $HOME, and so seem
hostile to the idea that anyone might not. There are scripts etc to try
to fix the directory paths to relocate the folder tree - they use one
for the bre-built binary - but I can't get it to work, or generate one
for Slackware
I give up. I'm dropping this turd.

Just a tip for anyone interested in take over maintenance for sage:
The AUR guys have made efforts to get the latest version (git) working
on Arch Linux (https://aur.archlinux.org/packages/sagemath-git/).
Well... there are up to 16 patches applied in order to get sage working :-P
Good look for the next sage maintainer...

Post by King Beowulf
I'm tired of getting (hate)emails.

It's sad to hear this kind of thing.
When a SlackBuild script doesn't work I don't blame its maintainer
because I know that some environmental variables can affect the build
(e.g.: mix SBo packages with software from other 3rdparty repos).

I've never tried to build sage from source because I have an
underpowered machine, and as I would install the sage just out of
curiosity it's not worth the effort.

Best wishes,

[King Beowulf]

On 08/09/2018 07:37 AM, Fellype do Nascimento wrote:
..snip...

Post by Fellype do Nascimento
The AUR guys have made efforts to get the latest version (git) working
on Arch Linux (https://aur.archlinux.org/packages/sagemath-git/).
Well... there are up to 16 patches applied in order to get sage working :-P
Good look for the next sage maintainer...

...snip...

16? That's double from last I checked. It just doesn't make any sense
to me do go to that trouble. It takes 4+ hrs on my best box to compile
- too long a cycle for me to test patches. To have to patch in order to
make a relocatable binary is just insane.

Here's another tip for my successor - never could get this to work:
https://github.com/sagemath/binary-pkg

Just to clarify:

Sagemath compile does work fine on Slackware stable and current as long
as you build in the final target directory.

I'm just a simple country chemist.

[Daniel Prosser]

Perhaps if upstream is fighting so hard to make it *not* possible to package
sage, the best course of action is just to honor their intent and stop trying
(take it off SBo). Just my two cents as someone who does not use it anyway (so
maybe it's actually only worth one cent).

Dan

Post by King Beowulf
..snip...

Post by Fellype do Nascimento
The AUR guys have made efforts to get the latest version (git) working
on Arch Linux (https://aur.archlinux.org/packages/sagemath-git/).
Well... there are up to 16 patches applied in order to get sage working :-P
Good look for the next sage maintainer...

...snip...
16? That's double from last I checked. It just doesn't make any sense
to me do go to that trouble. It takes 4+ hrs on my best box to compile
- too long a cycle for me to test patches. To have to patch in order to
make a relocatable binary is just insane.
https://github.com/sagemath/binary-pkg
Sagemath compile does work fine on Slackware stable and current as long
as you build in the final target directory.
I'm just a simple country chemist.

_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Didier Spaier]

Post by Daniel Prosser
Perhaps if upstream is fighting so hard to make it *not* possible to package
sage, the best course of action is just to honor their intent and stop trying
(take it off SBo). Just my two cents as someone who does not use it anyway (so
maybe it's actually only worth one cent).

I am not an user either, but I once compiled it as regular user just to check
its ability to make png files for graphs, for an actual (and blind) user.
I just asked this friend, he is currently using the 8.1 version.

As for maths there is nothing close to sage's features I'd suggest
not providing a SlackBuild but a README explaining the situation.

Just my 0.02€.
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://sla

[Didier Spaier]

I forgot: his user a set specific user "maths" for that.

Post by Didier Spaier

Post by Daniel Prosser
Perhaps if upstream is fighting so hard to make it *not* possible to package
sage, the best course of action is just to honor their intent and stop trying
(take it off SBo). Just my two cents as someone who does not use it anyway (so
maybe it's actually only worth one cent).

I am not an user either, but I once compiled it as regular user just to check
its ability to make png files for graphs, for an actual (and blind) user.
I just asked this friend, he is currently using the 8.1 version.
As for maths there is nothing close to sage's features I'd suggest
not providing a SlackBuild but a README explaining the situation.
Just my 0.02€.
_______________________________________________
SlackBuilds-users mailing list
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[JCA]

Why not use the Debian binary tarball that is available in the Sage
website? I have just tried (for Sage 8.3) and it seems to work fine. Here
is what I did:

1. As root, unpacked the tarball in /opt. This create /opt/SageMath.
2. cd /opt/SageMath.
3. ./sage. This patches up Sage's files (black magic?) and launches Sage.
You end up at the Sage CLI. It can be checked out that it works, at least
for simple operations - like, e.g. an integration.
4. Exit Sage.
5. cd /usr/local/bin.
6. ln -s /opt/SageMath/sage ./sage.
7. Exit root.
8. Assuming that /usr/local/bin is in your path, launch Sage by invoking
the sage command.
9. Verify that it works.

Assuming that the above keeps working when using more esoteric Sage
capabilities, getting a Slackbuilds script to do all that should be
straightforward. I haven't tried building for sources, but I find it
difficult to believe that the Debian binary tarball is created using some
knowledge available to members of the inner circle alone.

If I am missing something here please let me know.

Post by Didier Spaier
I forgot: his user a set specific user "maths" for that.

Post by Didier Spaier

Post by Daniel Prosser
Perhaps if upstream is fighting so hard to make it *not* possible to

package

Post by Didier Spaier

Post by Daniel Prosser
sage, the best course of action is just to honor their intent and stop

trying

Post by Didier Spaier

Post by Daniel Prosser
(take it off SBo). Just my two cents as someone who does not use it

anyway (so

Post by Didier Spaier

Post by Daniel Prosser
maybe it's actually only worth one cent).

I am not an user either, but I once compiled it as regular user just to

check

Post by Didier Spaier
its ability to make png files for graphs, for an actual (and blind) user.
I just asked this friend, he is currently using the 8.1 version.
As for maths there is nothing close to sage's features I'd suggest
not providing a SlackBuild but a README explaining the situation.
Just my 0.02€.
_______________________________________________
SlackBuilds-users mailing list
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

_______________________________________________
SlackBuilds-users mailing list
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Duncan Roe]

Post by JCA
Why not use the Debian binary tarball that is available in the Sage
website? I have just tried (for Sage 8.3) and it seems to work fine. Here
1. As root, unpacked the tarball in /opt. This create /opt/SageMath.
2. cd /opt/SageMath.
3. ./sage. This patches up Sage's files (black magic?) and launches Sage.
You end up at the Sage CLI. It can be checked out that it works, at least
for simple operations - like, e.g. an integration.
4. Exit Sage.
5. cd /usr/local/bin.
6. ln -s /opt/SageMath/sage ./sage.
7. Exit root.
8. Assuming that /usr/local/bin is in your path, launch Sage by invoking
the sage command.
9. Verify that it works.
Assuming that the above keeps working when using more esoteric Sage
capabilities, getting a Slackbuilds script to do all that should be
straightforward. I haven't tried building for sources, but I find it
difficult to believe that the Debian binary tarball is created using some
knowledge available to members of the inner circle alone.
If I am missing something here please let me know.

Hi JCA,

Sounds like it should be easy enough to automate into a build script using
mkchroot. I can give it a go (but I'm not a sage user). Could you please
clarify a couple if items:

1. Does ./sage really work after cd-ing to a freshly created directory?

2. I assume checking with an integration is not essential to the build process -
is that correct?

Cheers ... Duncan.

Post by JCA

Post by Didier Spaier
I forgot: his user a set specific user "maths" for that.

Post by Didier Spaier

Post by Daniel Prosser
Perhaps if upstream is fighting so hard to make it *not* possible to

package

Post by Didier Spaier

Post by Daniel Prosser
sage, the best course of action is just to honor their intent and stop

trying

Post by Didier Spaier

Post by Daniel Prosser
(take it off SBo). Just my two cents as someone who does not use it

anyway (so

Post by Didier Spaier

Post by Daniel Prosser
maybe it's actually only worth one cent).

I am not an user either, but I once compiled it as regular user just to

check

Post by Didier Spaier
its ability to make png files for graphs, for an actual (and blind) user.
I just asked this friend, he is currently using the 8.1 version.
As for maths there is nothing close to sage's features I'd suggest
not providing a SlackBuild but a README explaining the situation.
Just my 0.02???.

_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[JCA]

Post by Duncan Roe

Post by JCA
Why not use the Debian binary tarball that is available in the Sage
website? I have just tried (for Sage 8.3) and it seems to work fine. Here
1. As root, unpacked the tarball in /opt. This create /opt/SageMath.
2. cd /opt/SageMath.
3. ./sage. This patches up Sage's files (black magic?) and launches Sage.
You end up at the Sage CLI. It can be checked out that it works, at least
for simple operations - like, e.g. an integration.
4. Exit Sage.
5. cd /usr/local/bin.
6. ln -s /opt/SageMath/sage ./sage.
7. Exit root.
8. Assuming that /usr/local/bin is in your path, launch Sage by invoking
the sage command.
9. Verify that it works.
Assuming that the above keeps working when using more esoteric Sage
capabilities, getting a Slackbuilds script to do all that should be
straightforward. I haven't tried building for sources, but I find it
difficult to believe that the Debian binary tarball is created using some
knowledge available to members of the inner circle alone.
If I am missing something here please let me know.

Hi JCA,
Sounds like it should be easy enough to automate into a build script using
mkchroot. I can give it a go (but I'm not a sage user). Could you please
1. Does ./sage really work after cd-ing to a freshly created directory?

I am not sure I understand your question. What I describe allows one to
install the Sage executable under /usr/local/bin, and launch it from
anywhere, provided that /usr/local/bin is in your path. You would only
invoked ./sage from /usr/local/bin, but - why would you want to that?

Post by Duncan Roe
2. I assume checking with an integration is not essential to the build process -
is that correct?

That integration is nothing but a very basic functional test of the
installed product. I just used the Debian package - I did not build Sage
myself, for it takes ages and a serious system. I am merely pointing out
that, following the steps I described above, one ends up with a Sage
environment that seems to work fine, and one does not have to suffer the
punishment that the original maintainer described in order to install it in
a sensible location. I have tried a few other things in the resulting Sage,
and they all seem to work.

Post by Duncan Roe
Cheers ... Duncan.

Post by JCA

Post by Didier Spaier
I forgot: his user a set specific user "maths" for that.

Post by Didier Spaier

Post by Daniel Prosser
Perhaps if upstream is fighting so hard to make it *not* possible to

package

Post by Didier Spaier

Post by Daniel Prosser
sage, the best course of action is just to honor their intent and

stop

Post by JCA

Post by Didier Spaier
trying

Post by Didier Spaier

Post by Daniel Prosser
(take it off SBo). Just my two cents as someone who does not use it

anyway (so

Post by Didier Spaier

Post by Daniel Prosser
maybe it's actually only worth one cent).

I am not an user either, but I once compiled it as regular user just

to

Post by JCA

Post by Didier Spaier
check

Post by Didier Spaier
its ability to make png files for graphs, for an actual (and blind)

user.

Post by JCA

Post by Didier Spaier

Post by Didier Spaier
I just asked this friend, he is currently using the 8.1 version.
As for maths there is nothing close to sage's features I'd suggest
not providing a SlackBuild but a README explaining the situation.
Just my 0.02???.

_______________________________________________
SlackBuilds-users mailing list
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Duncan Roe]

Hi JCA,

Post by JCA

Post by Duncan Roe

Post by JCA
Why not use the Debian binary tarball that is available in the Sage
website? I have just tried (for Sage 8.3) and it seems to work fine. Here
1. As root, unpacked the tarball in /opt. This create /opt/SageMath.
2. cd /opt/SageMath.
3. ./sage. This patches up Sage's files (black magic?) and launches Sage.
You end up at the Sage CLI. It can be checked out that it works, at least
for simple operations - like, e.g. an integration.
4. Exit Sage.
5. cd /usr/local/bin.
6. ln -s /opt/SageMath/sage ./sage.
7. Exit root.
8. Assuming that /usr/local/bin is in your path, launch Sage by invoking
the sage command.
9. Verify that it works.
Assuming that the above keeps working when using more esoteric Sage
capabilities, getting a Slackbuilds script to do all that should be
straightforward. I haven't tried building for sources, but I find it
difficult to believe that the Debian binary tarball is created using some
knowledge available to members of the inner circle alone.
If I am missing something here please let me know.

Hi JCA,
Sounds like it should be easy enough to automate into a build script using
mkchroot. I can give it a go (but I'm not a sage user). Could you please
1. Does ./sage really work after cd-ing to a freshly created directory?

I am not sure I understand your question. What I describe allows one to
install the Sage executable under /usr/local/bin, and launch it from
anywhere, provided that /usr/local/bin is in your path. You would only
invoked ./sage from /usr/local/bin, but - why would you want to that?

Post by Duncan Roe
2. I assume checking with an integration is not essential to the build process -
is that correct?

That integration is nothing but a very basic functional test of the
installed product. I just used the Debian package - I did not build Sage
myself, for it takes ages and a serious system. I am merely pointing out
that, following the steps I described above, one ends up with a Sage
environment that seems to work fine, and one does not have to suffer the
punishment that the original maintainer described in order to install it in
a sensible location. I have tried a few other things in the resulting Sage,
and they all seem to work.

Post by Duncan Roe
Cheers ... Duncan.

Post by JCA

Post by Didier Spaier
I forgot: his user a set specific user "maths" for that.

Post by Didier Spaier

Post by Daniel Prosser
Perhaps if upstream is fighting so hard to make it *not* possible to

package

Post by Didier Spaier

Post by Daniel Prosser
sage, the best course of action is just to honor their intent and

stop

Post by JCA

Post by Didier Spaier
trying

Post by Didier Spaier

Post by Daniel Prosser
(take it off SBo). Just my two cents as someone who does not use it

anyway (so

Post by Didier Spaier

Post by Daniel Prosser
maybe it's actually only worth one cent).

I am not an user either, but I once compiled it as regular user just

to

Post by JCA

Post by Didier Spaier
check

Post by Didier Spaier
its ability to make png files for graphs, for an actual (and blind)

user.

Post by JCA

Post by Didier Spaier

Post by Didier Spaier
I just asked this friend, he is currently using the 8.1 version.
As for maths there is nothing close to sage's features I'd suggest
not providing a SlackBuild but a README explaining the situation.
Just my 0.02???.

Thanks for getting back with answers to my dumb questions and sorry for the
noise.

I went ahead and submitted (what became) sage-bin-8.3 (thanks for all the work,
mods) and it's been on SBO for just over a month now.

I guess I should have posted to this thread about that :/

It's a package of the Debian tarball as you suggested, installs (a symlink) in
/usr/bin works from anywhere etc. etc.

I did try some plots and they looked fine, but mostly I just (mis-)use it to do
proper-fraction arithmetic - it's great!

Cheers ... Duncan.
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[JCA]

Thanks for taking care of this. It sure beats having to build the beast
from scratch - which, unless one has a rather beefy machine, will take
forever. This aside from the relocation issues.

Post by Duncan Roe
Hi JCA,

Post by JCA

Post by Duncan Roe

Post by JCA
Why not use the Debian binary tarball that is available in the Sage
website? I have just tried (for Sage 8.3) and it seems to work fine.

Here

Post by JCA

Post by Duncan Roe

Post by JCA
1. As root, unpacked the tarball in /opt. This create /opt/SageMath.
2. cd /opt/SageMath.
3. ./sage. This patches up Sage's files (black magic?) and launches

Sage.

Post by JCA

Post by Duncan Roe

Post by JCA
You end up at the Sage CLI. It can be checked out that it works, at

least

Post by JCA

Post by Duncan Roe

Post by JCA
for simple operations - like, e.g. an integration.
4. Exit Sage.
5. cd /usr/local/bin.
6. ln -s /opt/SageMath/sage ./sage.
7. Exit root.
8. Assuming that /usr/local/bin is in your path, launch Sage by

invoking

Post by JCA

Post by Duncan Roe

Post by JCA
the sage command.
9. Verify that it works.
Assuming that the above keeps working when using more esoteric Sage
capabilities, getting a Slackbuilds script to do all that should be
straightforward. I haven't tried building for sources, but I find it
difficult to believe that the Debian binary tarball is created using

some

Post by JCA

Post by Duncan Roe

Post by JCA
knowledge available to members of the inner circle alone.
If I am missing something here please let me know.

Hi JCA,
Sounds like it should be easy enough to automate into a build script

using

Post by JCA

Post by Duncan Roe
mkchroot. I can give it a go (but I'm not a sage user). Could you

please

Post by JCA

Post by Duncan Roe
1. Does ./sage really work after cd-ing to a freshly created directory?

I am not sure I understand your question. What I describe allows one

to

Post by JCA
install the Sage executable under /usr/local/bin, and launch it from
anywhere, provided that /usr/local/bin is in your path. You would only
invoked ./sage from /usr/local/bin, but - why would you want to that?

Post by Duncan Roe
2. I assume checking with an integration is not essential to the build process -
is that correct?

That integration is nothing but a very basic functional test of the
installed product. I just used the Debian package - I did not build Sage
myself, for it takes ages and a serious system. I am merely pointing out
that, following the steps I described above, one ends up with a Sage
environment that seems to work fine, and one does not have to suffer the
punishment that the original maintainer described in order to install it

in

Post by JCA
a sensible location. I have tried a few other things in the resulting

Sage,

Post by JCA
and they all seem to work.

Post by Duncan Roe
Cheers ... Duncan.

Post by JCA

Post by Didier Spaier
I forgot: his user a set specific user "maths" for that.

Post by Didier Spaier

Post by Daniel Prosser
Perhaps if upstream is fighting so hard to make it *not*

possible to

Post by JCA

Post by Duncan Roe

Post by JCA

Post by Didier Spaier
package

Post by Didier Spaier

Post by Daniel Prosser
sage, the best course of action is just to honor their intent

and

Post by JCA

Post by Duncan Roe
stop

Post by JCA

Post by Didier Spaier
trying

Post by Didier Spaier

Post by Daniel Prosser
(take it off SBo). Just my two cents as someone who does not

use it

Post by JCA

Post by Duncan Roe

Post by JCA

Post by Didier Spaier
anyway (so

Post by Didier Spaier

Post by Daniel Prosser
maybe it's actually only worth one cent).

I am not an user either, but I once compiled it as regular user

just

Post by JCA

Post by Duncan Roe
to

Post by JCA

Post by Didier Spaier
check

Post by Didier Spaier
its ability to make png files for graphs, for an actual (and

blind)

Post by JCA

Post by Duncan Roe
user.

Post by JCA

Post by Didier Spaier

Post by Didier Spaier
I just asked this friend, he is currently using the 8.1 version.
As for maths there is nothing close to sage's features I'd

suggest

Post by JCA

Post by Duncan Roe

Post by JCA

Post by Didier Spaier

Post by Didier Spaier
not providing a SlackBuild but a README explaining the situation.
Just my 0.02???.

Thanks for getting back with answers to my dumb questions and sorry for the
noise.
I went ahead and submitted (what became) sage-bin-8.3 (thanks for all the work,
mods) and it's been on SBO for just over a month now.
I guess I should have posted to this thread about that :/
It's a package of the Debian tarball as you suggested, installs (a symlink) in
/usr/bin works from anywhere etc. etc.
I did try some plots and they looked fine, but mostly I just (mis-)use it to do
proper-fraction arithmetic - it's great!
Cheers ... Duncan.
_______________________________________________
SlackBuilds-users mailing list
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/