On Wednesday, June 12, 2019 at 2:05:04 PM UTC+2, E. Madison Bray wrote:
>
> One very easily solution to this, and I know some people will shudder
> (myself included) is to simply include the configure script in the
> repository.
We already have a way of bundling up the configure scripts in a tarball, we
may just as well use that. Its not used right now becaues a) monotonically
increasing version numbers for the confball are a pita, and b) we don't
want to put every temporary confball on the mirror network. E.g. if
somebody steps up and extends the bootstrap script to save/load based on
the git head sha1, e.g.:
./bootstrap --save-head
saves upstream/configure-<sha1>.tag.gz
./bootstrap --load-head http://path/to/upstream/
loads http://path/to/upstream/configure-<sha1>.tag.gz
then I can add them to the release script and buildbots...
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-release/9e00eb09-b985-4634-90b6-718931463a54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
