#12375: Create a giac package
-------------------------------------+-------------------------------------
Reporter: frederichan | Owner: tbd
Type: enhancement | Status: needs_review
Priority: minor | Milestone: sage-6.4
Component: packages: | Resolution:
optional | Merged in:
Keywords: giac | Reviewers: Dima Pasechnik,
Authors: Han Frederic | Jeroen Demeyer
Report Upstream: N/A | Work issues:
Branch: public/giac_spkg | Commit:
Dependencies: | d0cee55ac0759159ff985e2f3ab645310a174aba
| Stopgaps:
-------------------------------------+-------------------------------------
Comment (by dimpase):
Replying to [comment:99 parisse]:
> The problem is : it takes me a couple of hours at least to update
links/change scripts to recompile all the binaries (win32/64, mac, linux).
I don't want to loose that time each time a make a 5 minutes fix in the
code.
I don't understand: all you need to do to update the version number is to
change one line in `configure.in` (and then obviously rerun the whole
building process).
How does this take a couple of hours of your time, is hard to see.
What exactly do you need changed in your building procedure? And how would
making it dependent on e.g. the date make it any faster?
> I do that for major reasons (for example new code for computing Groebner
basis or have a new version number for French math teacher competitions
...). These steps could perhaps be automated but doing that myself would
probably make me crazy.
> The vast majority of my user basis are end users, they don't care at all
about the source tarball name, but they are very happy to get a fast
update of the binaries when they report a bug (often 1 or 2 days after).
And how often do they report a bug you already fixed, just because they
have no means to see if you did an update of the tarball?
> Perhaps a convenient solution for sage would be a wget on my site and
then the tarball name would be changed to giac-YYYYMMDD.tar.bz2.
This won't give Sage a way to keep it up to day, as we certainly would
have no idea whether a you did a hidden update of the tarball.
--
Ticket URL: <http://trac.sagemath.org/ticket/12375#comment:100>
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/d/optout.
