On Sun, Dec 15, 2013 at 04:53:12PM -0600, Dirk Eddelbuettel wrote: > | Happy to help if you want me to ;-) Github repo or alioth repo would > | be fine. I can do that if you'd like me to, but probably not before > | next weekend. > > One possible issue is that the same debian/* files are also used for the > fairly widely deployed "ports" distributed via CRAN. They take what I stick > into Debian unstable (where dpkg 1.17.2 may help) and rebuild for Debian > stable and the various Ubuntu flavours. I work pretty closely with the two > porters and would try to avoid creating extra work for them. But maybe they > then just need to comment-in/out the FFLAGS setting... > > No strong feeling re GH or Alioth. Maybe Alioth is easier.
Well, perhaps one could use code something like this (untested) to save having porters having to deal with this problem individually. Then when dpkg 1.17.2 is in oldstable, this can be done away with and just the --get FFLAGS line can be left. # dpkg 1.17.2 fixed a bug with the definition of FFLAGS in dpkg-buildflags dpkg_version = $(shell dpkg -s dpkg-dev | grep '^Version:' | cut -d' ' -f2) newdpkg = $(shell if dpkg --compare-versions $(dpkg_version) ge 1.17.2; then echo "yes"; else echo "no"; fi) ifeq ($newdpkg,"yes") fflags = $(shell dpkg-buildflags --get FFLAGS) else fflags = $(shell dpkg-buildflags --get CFLAGS) endif Julian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
