script packages should cd into the SPKG directory

[mkoeppe]

This simplifies several spkg-install scripts and make script packages a bit more similar to normal packages.

This is a step towards #29386 (Install script packages via sage-spkg).

Depends on #29345

CC: @jhpalmieri @embray @orlitzky @dimpase

Component: build

Author: Matthias Koeppe

Branch/Commit: 72346ef

Reviewer: Michael Orlitzky

Issue created by migration from https://trac.sagemath.org/ticket/29793

[mkoeppe]

Branch: u/mkoeppe/script_packages_should_cd_into_the_spkg_directory

[mkoeppe]

Commit: df3f05e

[mkoeppe]

Last 10 new commits:

fb475f3	Trac #29345: replace a few obsolete "-a" tests with "-e".
305d8cf	Trac #29345: replace a bash array with something portable.
d0dff56	Trac #29345: replace a few uses of "source" with "."
5ac420b	Trac #29345: fix some bashisms in sage-env's resolvelinks() function.
0a61795	Trac #29345: don't force SHELL=bash any longer.
5db5318	Trac #29345: remove "break" statements from AC_SEARCH_LIBS.
e810ad1	Trac #29345: don't use sage's config.status for the lrcalc build.
93c9921	Trac #29345: replace the function that populates the CVXOPT_* variables.
0e66a0a	Trac #29345: add Dima's SPKG patches for ksh compatibility.
df3f05e	build/make/Makefile.in [SCRIPT_PACKAGE_templ]: cd into the SPKG directory; adjust spkg-install scripts

[mkoeppe]

comment:3

Branch is on top of #29345. There is only 1 new commit.

[orlitzky]

Reviewer: Michael Orlitzky

[orlitzky]

comment:4

LGTM but is there some documentation that says what the initial working directory of spkg-install should be? It shouldn't be an implementation detail.

[mkoeppe]

comment:5

Indeed I forgot to update the documentation

[sagetrac-git]

Changed commit from df3f05e to 72346ef

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

72346ef

Update developer manual on script packages

[orlitzky]

comment:8

Even better.

[mkoeppe]

comment:9

Thank you!