#14792: source deleted after package build
-----------------------------------+---------------------------
Reporter: felixs | Owner: GeorgSWeber
Type: enhancement | Status: new
Priority: minor | Milestone: sage-5.12
Component: build | Resolution:
Keywords: build src clean | Merged in:
Authors: Felix Salfelder | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-----------------------------------+---------------------------
Comment (by felixs):
Replying to [comment:3 leif]:
> Another odd thing is that you can't just test an spkg (after it's been
built / installed) even if you kept its build directory [other than by
starting a Sage subshell, changing to the directory and running `./spkg-
check`].
Package operations must be controlled from toplevel. The packages don't
know their dependencies (currently), and spkg-install files are not in a
shape to do anything else. Running checks can be done with `make
<packagename>-check` (in my implementation).
> And rerunning (parts of) `spkg-install` is usually also an adventure.
The spkg-install programs must be idempotent (of course). Just like `make
install` is for all sane packages. (It's not hard to fix this!).
I think I should add something like `AC_ARG_ENABLE([keepbuilt]...)`. I
don't see a reason why it should be disabled in case `.git` is present.
How are rebuilds caused by branch change implemented/handled currently?
--
Ticket URL: <http://trac.sagemath.org/ticket/14792#comment:4>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.
