#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:101 parisse]:
> Changing the tarball name would not impact too much (I would have to
remove old archives from time to time and taking care when saving the
tarball to an USB key), but changing the directory name stored inside the
tarball has more impact, I need to modify build scripts, move build
directories and update links, and sometimes rebuild all the source instead
of recompiling a few modified files.
> Most users reporting bugs do not compile giac themselves, they are using
geogebra, the HP Prime calculator and report on respectives forums or Xcas
binaries and report on Xcas forum.
> I don't understand what's the problem on sage side, why not take the
latest stable archive from my site when you are doing a compilation? Why
is it so important to have a different tarball number on my site each time
I make a fix? You can add any stamp you want on your side with the date or
sage release number or whatever. That's the way geogebra works, they are
just building with the latest SVN revision of giac, and they add their own
release number.
The problem is that we do not want bug reports related to a version we
have no good means to track. Indeed, it would look as follows: we get a
bug report, on giac version x.y.z. But because x.y.z is not frozen, such a
report needs to be tested with "latest" x.y.z.
And would would be the means to check that "latest" x.y.z is different
from the one we have supplied? None, short of comparing the sources file
by file...
I looked at what geogebra does. You have commits into their SVN tree, in
the trunk. How do your tarballs relate to what they release, and how to
extract what we need from there, it's not clear at all.
Do you have a separate RCS repo somewhere? I don't see any links to it on
your giac pages, and geogebra on
https://dev.geogebra.org/trac/wiki/SourcesForUsedLibraries just points to
your homepage, and it has no pointers to the source (why?). While you
actually seem to be comitting directly to the geogebra source tree...
--
Ticket URL: <http://trac.sagemath.org/ticket/12375#comment:102>
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.
