"configure" was deliberately made a separate, manual step because users need to read (and act upon) its output.
On Sunday, April 24, 2022 at 10:21:45 PM UTC-7 hohoa...@gmail.com wrote: > P.S: > """ > Everyone wants the top-level "sage" script to work out of the box > without being configured, built, or installed > """ > > Maybe experienced users in this camp can share some undocumented use > case scenarios? > > While waiting for someone to share their secrets, It was found that the > "advanced incantations" is missing some important pieces, > (like '*sage -cbr*" "Configure&Build&Run" so that advanced users do not > have to face questions like "Did you run configure?" > > On Saturday, April 23, 2022 at 8:10:37 PM UTC-4 ph h wrote: > >> Hi, >> >> Thank you for your responses. >> >> > Yes, in modern Python packaging, all installation goes through building >> wheels -- so the final installation location is not known at build time. >> > (Although in the Sage distribution, we are not quite there yet -- see >> https://trac.sagemath.org/ticket/32874) >> >> > in suffixes are standard (e.g. Makefile.in is the standard name for a >> file generated by automake). >> > These files often contain templates, which are substituted by >> ./configure with actual values, >> > they are seldom something one sources, in the unix shell sense. >> >> Your guidance is much appreciated. >> >> Regards, >> >> phiho >> >> >> On Sat, Apr 23, 2022 at 5:14 PM Dima Pasechnik <dim...@gmail.com> wrote: >> >>> >>> >>> On Sat, 23 Apr 2022, 19:00 ph h, <hohoa...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> Thank you for your response. >>>> >>>> > Note: the ".in" suffix doesn't mean "include," by convention it >>>> roughly >>>> > means "a file that will be processed by ./configure". So, for example, >>>> > Makefile.in gets turned into Makefile when you run ./configure. >>>> >>>> So, to avoid confusion, ".in" should be ".src", just to be "sourced"? >>>> >>> >>> .in suffixes are standard (e.g. Makefile.in is the standard name for a >>> file generated by automake). These files often contain templates, which are >>> substituted by ./configure with actual values, they are seldom something >>> one sources, in the unix shell sense. >>> >>> >>> >>>> >>>> > 2. Everyone wants the top-level "sage" script to work out of the box >>>> > without being configured, built, or installed. Within "sage", >>>> > then, how can you know where to look for the resolvelinks.sh >>>> > file? You can't use $0 if $0 is a link unless you know how to >>>> > resolve it >>>> >>>> WOW, without running even 'make configure'? >>>> Is the distributed tarball already pre-configured ('configure" is >>>> included)? >>>> >>>> > In general: just go try it and see what breaks. >>>> >>>> Try what? >>>> >>>> Maybe experienced users in this camp can share some undocumented use >>>> case scenarios? >>>> To be clear, what would they like to do with a copy of SageMath just >>>> freshly checked out from github and how to verify that "it works" out of >>>> the box >>>> Maybe these people just use the pre-configured tarball because they may >>>> not be familiar with github? >>>> >>>> Regards, >>>> >>>> phiho >>>> >>>> >>>> On Sat, Apr 23, 2022 at 12:08 PM Michael Orlitzky <mic...@orlitzky.com> >>>> wrote: >>>> >>>>> On Sat, 2022-04-23 at 08:28 -0400, ph h wrote: >>>>> > Dear All, >>>>> > >>>>> > If the three files: >>>>> > >>>>> > 1. sage/sage >>>>> > 2. sage/src/bin/sage >>>>> > 3. sage/src/bin/sage-env >>>>> > >>>>> > are to be factored out into >>>>> > >>>>> > 1. sage/resolvelinks.in >>>>> > 2. sage/sage.sage.in >>>>> > 3. sage/sage.src.bin.sage.in >>>>> > 4. sage/sage.src.bin.sage-env.in >>>>> > >>>>> >>>>> Note: the ".in" suffix doesn't mean "include," by convention it roughly >>>>> means "a file that will be processed by ./configure". So, for example, >>>>> Makefile.in gets turned into Makefile when you run ./configure. >>>>> >>>>> >>>>> > >>>>> > Please advise how can this attempt be tested: >>>>> > >>>>> > 1. Before 'make configure' is run at $SAGE_ROOT >>>>> > 2. Before './configure' is run at $SAGE_ROOT >>>>> > 3. Before 'make' is run at $SAGE_ROOT >>>>> > 4. After installation is completed >>>>> > >>>>> > >>>>> >>>>> In general: just go try it and see what breaks. Here there are two >>>>> problems: >>>>> >>>>> 1. The python build system apparently can't make the right path >>>>> substitutions (like autotools could), and we use the python >>>>> build system for the bits relevant to these files. >>>>> >>>>> 2. Everyone wants the top-level "sage" script to work out of the box >>>>> without being configured, built, or installed. Within "sage", >>>>> then, how can you know where to look for the resolvelinks.sh >>>>> file? You can't use $0 if $0 is a link unless you know how to >>>>> resolve it. >>>>> >>>>> >>>>> >>>>> -- >>>>> 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+...@googlegroups.com. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/sage-devel/fdf2f4cb66ed9f5af12435c8425e3094f81e8660.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+...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/sage-devel/CALZQg1azkPhWjnVuv9rD0PiEMRYdROr75e2WhdxrBj_J7BcYOA%40mail.gmail.com >>>> >>>> <https://groups.google.com/d/msgid/sage-devel/CALZQg1azkPhWjnVuv9rD0PiEMRYdROr75e2WhdxrBj_J7BcYOA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >>> 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+...@googlegroups.com. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/sage-devel/CAAWYfq3jUC%3DY6r%2Bvy%3DA27xApKO0BNcOg-Lk9yhu_%3D%3Do%2BpkzZJA%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/sage-devel/CAAWYfq3jUC%3DY6r%2Bvy%3DA27xApKO0BNcOg-Lk9yhu_%3D%3Do%2BpkzZJA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- 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/e190d6f4-105a-4f03-9e2d-1d84dbf35aa3n%40googlegroups.com.
