Re: [sage-devel] Proposal: make Jupyterlab a standard package
Hi, On Tue, Mar 22, 2022 at 10:51:06AM -0400, Michael Orlitzky wrote: > On Tue, 2022-03-22 at 13:47 +, Thierry wrote: > > > > "Standard" also means "be shipped within the source tarball" that is > > self-contained and does not require network connexion to be installed. > > > > True, but it would be just as easy to ship the tarballs for packages > that are optional and enabled by default as it is to ship them for > packages that are standard. I just wanted to point that we still need a "standard vs optional" distinction for this purpose. Regarding make options, maybe it could be nice to ship all possible make options (--enable-*, --disable-*) for every package, so that we can override defaults easily ? Ciao, Thierry > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/2a6bcb9cceae2a8bbc0724dfdab903e49213bada.camel%40orlitzky.com. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/20220322153710.GA24034%40metelu.net.
Re: [sage-devel] Proposal: make Jupyterlab a standard package
+1 for enabling JuptyerLab by default. There is already a ticket to make it a standard spkg: https://trac.sagemath.org/ticket/24904 -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/0d57c31a-0dcc-4697-a5a9-642488ef3c97n%40googlegroups.com.
Re: [sage-devel] Proposal: make Jupyterlab a standard package
On Tue, 2022-03-22 at 13:47 +, Thierry wrote: > > "Standard" also means "be shipped within the source tarball" that is > self-contained and does not require network connexion to be installed. > True, but it would be just as easy to ship the tarballs for packages that are optional and enabled by default as it is to ship them for packages that are standard. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/2a6bcb9cceae2a8bbc0724dfdab903e49213bada.camel%40orlitzky.com.
Re: [sage-devel] Proposal: make Jupyterlab a standard package
Hi, On Tue, Mar 22, 2022 at 07:58:07AM -0400, Michael Orlitzky wrote: > On Tue, 2022-03-22 at 03:44 -0700, Eric Gourgoulhon wrote: > > > > Maybe it is time to make it a standard package in Sage. > > > > If so, please make it optional via a --disable-jupyterlab flag. (We > already have one for the standard notebook, --disable-notebook.) > > Hijack, sorry: with these flags starting to accumulate, now would be a > good time to go back and make sense of our standard vs optional > designation. In most packages, anything that has a --disable flag is > de-facto optional, but the default (enabled or disabled) can be set > per-package. In sage, we use "optional" to mean "optional and disabled > by default." Historically "standard" has meant "not optional and > therefore always enabled," but more and more these days it means > "optional but enabled by default." "Standard" also means "be shipped within the source tarball" that is self-contained and does not require network connexion to be installed. Ciao, Thierry > I think anything that can be disabled (such as jupyterlab) should be > "optional," but that we should be able to mark optional packages as > enabled by default. So the "optional" distinction would just mean "give > it a ./configure flag." This would avoid the semantic confusion of > "standard" packages that can be disabled via hand-written --disable > flags. > > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/1f0514f25545ddd9bdd1d875746ebf7bbdb2af07.camel%40orlitzky.com. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/20220322134711.GA22346%40metelu.net.
Re: [sage-devel] Proposal: make Jupyterlab a standard package
On Tue, 2022-03-22 at 03:44 -0700, Eric Gourgoulhon wrote: > > Maybe it is time to make it a standard package in Sage. > If so, please make it optional via a --disable-jupyterlab flag. (We already have one for the standard notebook, --disable-notebook.) Hijack, sorry: with these flags starting to accumulate, now would be a good time to go back and make sense of our standard vs optional designation. In most packages, anything that has a --disable flag is de-facto optional, but the default (enabled or disabled) can be set per-package. In sage, we use "optional" to mean "optional and disabled by default." Historically "standard" has meant "not optional and therefore always enabled," but more and more these days it means "optional but enabled by default." I think anything that can be disabled (such as jupyterlab) should be "optional," but that we should be able to mark optional packages as enabled by default. So the "optional" distinction would just mean "give it a ./configure flag." This would avoid the semantic confusion of "standard" packages that can be disabled via hand-written --disable flags. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/1f0514f25545ddd9bdd1d875746ebf7bbdb2af07.camel%40orlitzky.com.
