Bug#704805: Bug#726913: r-base-dev: does not use the dpkg-buildflags options for gfortran, specifically LDFLAGS

2014-04-05 Thread Dirk Eddelbuettel
On 5 April 2014 at 02:48, Vincent Danjean wrote: | On 04/04/2014 16:27, Dirk Eddelbuettel wrote: | | It would also mean that the critical r-base transition to testing can | | only happen when all of the depending add-on packages have been | | upgraded or removed from testing, making the

Bug#704805: Bug#726913: r-base-dev: does not use the dpkg-buildflags options for gfortran, specifically LDFLAGS

2014-04-04 Thread Julian Gilbey
[Moving to correct bug report from #726913] On Thu, Apr 03, 2014 at 06:45:57PM -0500, Dirk Eddelbuettel wrote: | The last major breakage happened when R went from 2.15.x - 3.0.x; R | 3.0.0 would not read packages built for R 2.15.x. Before that, it was | something like 2.9.x - 2.10.x (though

Bug#704805: Bug#726913: r-base-dev: does not use the dpkg-buildflags options for gfortran, specifically LDFLAGS

2014-04-04 Thread Dirk Eddelbuettel
On 4 April 2014 at 09:52, Julian Gilbey wrote: | Some examples of other packages which use this system (some calling it | -abi and others -api): | | apache2-bin, banshee, geany, libhdb9-heimdal, python-numpy, | python-sip, erlang-base Appreciate the list. That is helpful. | It would also mean

Bug#704805: Bug#726913: r-base-dev: does not use the dpkg-buildflags options for gfortran, specifically LDFLAGS

2014-04-04 Thread Vincent Danjean
On 04/04/2014 16:27, Dirk Eddelbuettel wrote: | It would also mean that the critical r-base transition to testing can | only happen when all of the depending add-on packages have been | upgraded or removed from testing, making the transition far, far | smoother. Yes, it may only happen once