>
> And for what it is worth, I very strongly believe we should do
> everything we can to transition Sage itself over to using current
> standard current approaches to development and distribution. That
> means fully supporting pip, using github (instead of a custom trac and
> wiki install),
On Mon, Aug 10, 2015 at 4:26 PM, Ondřej Čertík wrote:
> What is the best way to maintain a package like this for Sage --- we
> currently create an spkg, but I read somewhere that spkgs will be
> deprecated? Right now we want to maintain it ourselves and make it
> easy for people to try out and if
Hi Ondřej,
Old fashioned .spkg are not in fashion anymore. In fact we very much
want to kill them as much as possible. The new process separate the
tarball from upstream (pristine as much as possible) and the building
script. In a similar fashion gentoo ebuild or hashtag recipe. Look at
https:
Hi,
We just released SymEngine 0.1.0:
https://github.com/sympy/symengine/releases/tag/v0.1.0
SymEngine (https://github.com/sympy/symengine) is a standalone fast
C++ symbolic manipulation library. Optional thin wrappers allow usage
of the library from other languages, we currently have C, Python,
