Re: [sage-devel] Re: Package installation/uninstallation confusion

2019-11-06 Thread Dima Pasechnik
On Wed, Nov 6, 2019 at 7:17 PM John H Palmieri wrote: > > Simon, you should look at the json file for p_group_cohomology to see if it > contains all of the installed files, or if indeed some are not listed. If > everything is there, there is no need to split it into two packages, unless > I'm m

Re: [sage-devel] Re: Package installation/uninstallation confusion

2019-11-06 Thread John H Palmieri
Simon, you should look at the json file for p_group_cohomology to see if it contains all of the installed files, or if indeed some are not listed. If everything is there, there is no need to split it into two packages, unless I'm missing something. On Wednesday, November 6, 2019 at 9:33:04 AM

Re: [sage-devel] Re: Package installation/uninstallation confusion

2019-11-06 Thread Dima Pasechnik
sdh_install installs a json file into SAGE_LOCAL/var/lib/sage/installed/ which are then used by unistallaller e.g. "make meataxe" produces SAGE_LOCAL/var/lib/sage/installed/meataxe-1.0.p0 { "package_name": "meataxe", "package_version": "1.0.p0", "install_date": "Wed Nov 6 17:24:57 GMT

[sage-devel] Re: Package installation/uninstallation confusion

2019-11-06 Thread Simon King
Hi Eric, On 2019-11-06, E. Madison Bray wrote: >> However, I heard rumours that in order to make a Sage optional package >> uninstallable, one needs some new script analogous to spkg-install. >> >> Can someone give me a pointer on what should be done in that script and >> what tools (sdh_*) are a

Re: [sage-devel] building Sage docs on small VMs

2019-11-06 Thread Dima Pasechnik
On Wed, Nov 6, 2019 at 12:50 PM E. Madison Bray wrote: > > On Mon, Nov 4, 2019 at 2:00 PM Dima Pasechnik wrote: > > > > How does one switch off multiprocessing in docbuild? > > (it's ludicrous not being able to build docs on a VM with 2GB of memory) > > The variable you're looking for I think is

Re: [sage-devel] building Sage docs on small VMs

2019-11-06 Thread E. Madison Bray
On Mon, Nov 4, 2019 at 2:00 PM Dima Pasechnik wrote: > > How does one switch off multiprocessing in docbuild? > (it's ludicrous not being able to build docs on a VM with 2GB of memory) The variable you're looking for I think is SAGE_NUM_THREADS=1 (note: I think it will still fork at least once ev

Re: [sage-devel] Can we adopt "orphan" Sage-related packages ?

2019-11-06 Thread Emmanuel Charpentier
Okay. Now these very useful tools can be properly maintained. Thank you, Sho. Thank you, Dima. Le mercredi 6 novembre 2019 13:34:49 UTC+1, Dima Pasechnik a écrit : > > On Wed, Nov 6, 2019 at 11:05 AM Sho Takemori > wrote: > > > > Thank you very much for transferring. > > > > > PS. I notice t

Re: [sage-devel] Re: Package installation/uninstallation confusion

2019-11-06 Thread E. Madison Bray
On Wed, Nov 6, 2019 at 7:58 AM Simon King wrote: > > On 2019-11-05, E. Madison Bray wrote: > > The generated file `build/make/Makefile` is output by the > > `./configure` script. In fact, that's its main purpose. When > > switching branches in this case the best thing to do is to re-run > > `./

Re: [sage-devel] Can we adopt "orphan" Sage-related packages ?

2019-11-06 Thread Dima Pasechnik
On Wed, Nov 6, 2019 at 11:05 AM Sho Takemori wrote: > > Thank you very much for transferring. > > > PS. I notice that sage-shell-mode misses a license. Should we add one (GPL > > 3.0, as for all the other emacs lisp stuff we have). > > In the header of each file, it states it is under GPL v3.0,

Re: [sage-devel] Can we adopt "orphan" Sage-related packages ?

2019-11-06 Thread Sho Takemori
Thank you very much for transferring. > PS. I notice that sage-shell-mode misses a license. Should we add one (GPL 3.0, as for all the other emacs lisp stuff we have). In the header of each file, it states it is under GPL v3.0, but to make sure I have just added a LICENSE file. -- You rece

Re: [sage-devel] Can we adopt "orphan" Sage-related packages ?

2019-11-06 Thread Dima Pasechnik
Dear Sho, dear all, the repos in question are now under SageMath Github org. https://github.com/sagemath?utf8=%E2%9C%93&q=&type=&language=emacs+lisp Thanks again to Sho for the contributions to SageMath over the years. Best, Dima PS. I notice that sage-shell-mode misses a license. Should we add

Re: [sage-devel] Can we adopt "orphan" Sage-related packages ?

2019-11-06 Thread Dima Pasechnik
Yes please, thanks a lot in advance. Your contributions are very valuable for SageMath project. On Wed, Nov 6, 2019 at 9:20 AM Sho Takemori wrote: > > To transfer elisp repositories to the sagemath organization, a second step > transferring is necessary because I do not have a permission > (plea

Re: [sage-devel] Can we adopt "orphan" Sage-related packages ?

2019-11-06 Thread Sho Takemori
To transfer elisp repositories to the sagemath organization, a second step transferring is necessary because I do not have a permission (please refer to https://help.github.com/en/github/administering-a-repository/transferring-a-repository#about-repository-transfers ) for detail. I will transfe

Re: [sage-devel] Can we adopt "orphan" Sage-related packages ?

2019-11-06 Thread Sho Takemori
Thank you for the info. Then, I will transfer them to @dimpase on github. -- 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.