Hi,
Thanks for the link but it is way above her head right now.
Thanks for your support, anyway.
Regards,
phiho
On Fri, May 27, 2022 at 5:39 PM John H Palmieri
wrote:
> The development process and the trac server are documented at
> https://doc.sagemath.org/html/en/developer/trac.html#the-s
The development process and the trac server are documented at
https://doc.sagemath.org/html/en/developer/trac.html#the-sage-trac-server.
On Friday, May 27, 2022 at 12:30:38 PM UTC-7 Matthias Koeppe wrote:
> On Friday, May 27, 2022 at 12:08:54 PM UTC-7 hohoa...@gmail.com wrote:
>
>>
>> > Please
On Friday, May 27, 2022 at 12:08:54 PM UTC-7 hohoa...@gmail.com wrote:
>
> > Please open a ticket for it.
> Thank you for the encouragement but this hitchhiker has admitted her
> weakness with the ticket system.
> It is just a copy and paste snippet, maybe those who are in charge of '
> configur
Hi,
> bootstrap should work just fine from a path with spaces. (Test this on
top of the work that is already done -
https://trac.sagemath.org/ticket/33852)
Thst''s good to know. Apparently it has not been merged into Sage 9.7 Beta1
yet.
Looking forward to the merge.
Cheers,
phiho
On Fri, May
Hi,
> Please open a ticket for it.
Thank you for the encouragement but this hitchhiker has admitted her
weakness with the ticket system.
It is just a copy and paste snippet, maybe those who are in charge of '
configure.ac' could help with the ticket issue?
All the best,
phiho
On Fri, May 27,
bootstrap should work just fine from a path with spaces. (Test this on top
of the work that is already done - https://trac.sagemath.org/ticket/33852)
On Friday, May 27, 2022 at 11:57:30 AM UTC-7 hohoa...@gmail.com wrote:
> Hi,
>
> Thanks for the clarification.
> Does that do anything bad for t
Hi,
Thanks for the clarification.
Does that do anything bad for the source distribution or anything positive
for the github checkout?
Regards,
phiho
On Fri, May 27, 2022 at 2:42 PM Matthias Koeppe
wrote:
> The check during "bootstrap" would not help because the files that
> bootstrap generat
Yes, such checks in "configure.ac" would be a good idea. Please open a
ticket for it.
On Friday, May 27, 2022 at 4:33:14 AM UTC-7 hohoa...@gmail.com wrote:
> Hi,
>
> Maybe the tests with "contains_spaces()" in 'src/bin/sage-env' can be
> replaced with the followings in 'configure.ac' (after lin
The check during "bootstrap" would not help because the files that
bootstrap generates go into a source distribution.
On Friday, May 27, 2022 at 5:28:53 AM UTC-7 hohoa...@gmail.com wrote:
> P.S: Would this snippet in 'bootstrap' (below SAGE_ROOT=...) help, too:
>
> # Set SAGE_ROOT to the path to
PPS: Just FYI, before the above snippet was roughed in, "make configure"
from "$SAGE_ROOT" with embedded spaces indicates
that "$SYSTEM_PACKAGES_FILE" need be properly quoted in
"build/bin/sage-get-system-packages" and "src/doc/bootstrap", at least(?)
It couldn't be figured out why tons of sed 's
P.S: Would this snippet in 'bootstrap' (below SAGE_ROOT=...) help, too:
# Set SAGE_ROOT to the path to this file and then cd into it
SAGE_ROOT="$(cd "$(dirname "$0")" && pwd -P)"
# Check that we are not building in a directory containing spaces
if echo "$SAGE_ROOT" | grep " " > /dev/null ; then
Hi,
Maybe the tests with "contains_spaces()" in 'src/bin/sage-env' can be
replaced with the followings in 'configure.ac' (after line 75,
SAGE_LOCAL="$prefix"):
*http://configure.ac>>*
# Check that we are not building in a directory containing spaces
AS_IF([echo "$ac_pwd" |grep " " >/dev/null],
On Tuesday, May 24, 2022 at 3:11:00 PM UTC-7 hohoa...@gmail.com wrote:
> Does this apply only to "$SAGE_ROOT"?
> Can sub-directories of "$SAGE_ROOT" (like "lo space cal") contain spaces?
> Is it OK for $SAGE_LOCAL to contain spaces? If it is so, why the
> differences?
>
We do not systematically
13 matches
Mail list logo
