On Wed, Jul 20, 2016 at 10:11:11AM +0200, Sylvestre Ledru wrote: > Le 20/07/2016 à 09:44, Helmut Grohne a écrit : > > Given that the dependency is relevant to backporters and that 3.9 will > > eventually transition to a stable release, I think that simply adding > > the version constraint is the best route forward. > I understand you concern but I have a different issue. > I am using the same debian repo for http://apt.llvm.org/ > As I am supporting old Ubuntu distro, your patch is going to break the > dependencies as cmake is not available. > (I am using an upstream cmake tarball). > > Would you have a workaround which could fix that?
Given the contradictory requirements I don't see a good way. The only way to upload the same d/control for both precise and sid seems to be some kind of conditional. Those conditionals are commonly called "build profiles", but I fear that precise doesn't support build profiles. The cleanest approach seems to be to actually ship different d/control for precise and sid. That boils down to have a d/rules target for generating d/control though and adds more load. Given that I didn't know your requirements, maybe this bug is not worth fixing until precise is recycled, which seems to be April 2017. Helmut
