On Tue, Aug 21, 2018 at 5:49 PM, Duncan Roe <duncan_...@optusnet.com.au> wrote:
> On Mon, Aug 13, 2018 at 09:08:46AM -0600, JCA wrote: > > 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. > > > 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? > 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? > > 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. > Cheers ... Duncan. > > > > On Fri, Aug 10, 2018 at 11:26 AM, Didier Spaier <did...@slint.fr> wrote: > > > > > I forgot: his user a set specific user "maths" for that. > > > > > > On 08/10/2018 07:23 PM, Didier Spaier wrote: > > > > > > > > On 08/10/2018 04:22 AM, Daniel Prosser wrote: > > > >> 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-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/