RE : SAGE in Debian status page
Hello Alexander
> The API is (at least should be) compatible within the PolyBoRi 0.8 series.
to check for all this it would be nice to provide a symbol file.
I know that this is a huge work but as your are the upstream of the project, this should be not that hard.
look here [1] for the symbol file. This would help
> I see that you release 3 to 4 version of PolyBory each years. The minimum life time of a Debian release is 2,5 years.
> So it means, that you ask to import almost 10 different packages
> libpolybori-x.y.z in the archive during this time.
This will probably not the case. There will at most two really new
feature releases, but possibly some more bugfix releases.
bug fix release are not a problem if they are just bugfix without ABI breakage :)
> did you plan to support a special version of Polybori on a longer time period.
> Is the 0.8.2 this version or should we wait for the 1.y.z version. ?
0.8 fixed some design issue and 0.8.1 and 0.8.2 were mainly bug fixes
and additional minor features (like ipbori's self testing) for improving
stability. But 0.8.2 is mature enough, that we will see only bugfixes in
the next months. So I'd start with 0.8.2 now.
ok, can you activate the test suite during the build.
It is always good to run the test during the build process and abort if they failed.
This would help also a lot for th eport to the multiple architectures supported by Debian.
> This would be fine for me.
ok, so let's say
once you added the test suite, multiarch and the symbol file.
I would upload to experimental. Is it ok for you ?
can you use this verison number for experimental: 0.8.2-1~exp1
> I've added Breaks and Replaces to the control file (see repository).
you can chek that transition is smooth with piuparts.
> libpolybori-groebner depends on libpolybori. So this does not apply,
> does it?
If I were you I would split cleanly both library with there own
-dev
-deb
> Definitively. What do you suggest?
it depends of the platform you want to support.
unix/linux autotools and distutils for the python part
MacOS/windows maybe using cmake, distutils
the best choice to my opinion is between autotools/cmake.
for python modules the best practice is to provide a setup.py file.
but it require to split the source into the c++ libraries and another for the python binding.
is it possible ?
> > since you switch to compat level 9, it would be nice to provide a multiarchify package.
> > But with scons it will be difficult...
> It worked out well on Gentoo prefix, but maybe one has to adopt their
> patches to scons.
to my opinion it is not plan to pacth scons for the multy arch goal...
It is even explicitely propose to avoid scons for upstream ;)
> > can you provide also a pkg-config file [3] to help configure other project using your libraries.
> > a polybori.pc
> A added a .pc builder to the buld system and added it to the rules.
great but I can not find this .pc file in the -dev package.
you need also to install the .pc infile under
/usr/lib/<triplet>/pkgconfig directory
I saw this in your install files
+#! /usr/bin/dh-exec
+debian/tmp/usr/lib/*/*polybori-*.so.* usr/lib/${DEB_HOST_MULTIARCH}/
juste remove this dh-exec and use only this line instead of this.
usr/lib/*/*polybori-*.so.
you do not rename any file here.
> Also, I started multiarching. It went well on my system, but it would be
> interesting to see how it behaves in the wild. (I'm not sure whether I
> got the python paths right in general.)
we will see.
cheers
Frederic
[1] http://wiki.debian.org/UsingSymbolsFiles
Reply to: