[Debian-med-packaging] Status of igraph packaging for Debian

[Andreas Tille]

Hi Tamás,

On Mon, Aug 11, 2014 at 04:10:16PM +0200, Tamás Nepusz wrote:
>  
> Hi Andreas,
> 
> > I admit I did not downloaded from this location but rather from the  
> > Github releases at:  
> >  
> > https://github.com/igraph/igraph/releases  
> 
> I think these are automatically generated by Github whenever we tag a particular revision with a version number, and they simply contain the snapshots of the repository at that particular tag. (That's why these tarballs do not contain a ./configure script for instance - one still has to run autotools to get the configure script). Theoretically, you could get the "official" tarballs by checking out the corresponding snapshot from Github and then running "./bootstrap.sh" followed by "make dist", but it is easier to download the official tarballs from the following URLs:
> 
> http://igraph.org/c/#downloads
> 
> Right now the tarballs are built on our nightly build server, and you can always get the tarball containing version X.Y.Z using the url http://igraph.org/nightly/get/c/igraph-X.Y.Z.tar.gz. But I think that it's safer to watch http://igraph.org/c/#downloads in your watchfile in case we change the URL of the nightly build server from http://igraph.org/nightly to something else.

OK, I have updated debian/watch file (please checkout svn[1]).  I'd
suggest to always use this for packaging issues and keep us (= the
Debian Med team) informed about needed changes.  The new version was
just uploaded to unstable.
 
> > Regarding to update igraph in Debian it would be really welcome if you  
> > would maintain the official debian/ dir at svn.debian.org  
> 
> Let me take a look at the packaging policy so I could see how much effort/commitment this will require on my side; in particular, I was wondering whether it's okay for me to do this as I am not a daily Debian user any more. I could of course run Debian in a VM to test the package and fix things when something breaks, but if you think this is a problem, let me know.

For the moment there is no intervention needed since the packaging
worked quite nicely with your "correct" upstream source tarball.

What I would be really wondering is the Role of R igraph.  I realised
that it contains a code copy of (c-)igraph which is somehow against
Debian policy.  Is there any chance to use dynamic linking with
libigraph0 to avoid this code duplication?

Kind regards

        Andreas.

[1] svn://anonscm.debian.org/debian-med/trunk/packages/igraph/trunk/

-- 
http://fam-tille.de