On Thu, 2015-04-16 at 14:25 +0530, Arun Raghavan wrote: > On 16 April 2015 at 14:23, Tanu Kaskinen <tanu.kaskinen at linux.intel.com> wrote: > > On Wed, 2015-04-15 at 12:43 -0300, Felipe Sateler wrote: > >> But some reasons for installing packages explicitly: > >> > >> 1. Not in build-dep (git-core, check) > >> 2. Version upgrade after adding the trusty repositories. The build > >> failed if I didn't upgrade the autotools before building (not sure > >> why). > > > > So "apt-get build-dep" doesn't automatically upgrade all dependencies if > > they're already installed? And you didn't want to do a full system > > upgrade from 12.04 to 14.04. > > > >> 3. Me being lazy. dh-autoreconf is not used but I know it brings in > >> all the required deps for running autotools (we use that in the debian > >> package). > >> > >> Some pruning may be possible, but perhaps it is better to scrap the > >> build-dep and be explicit on what is depended upon. > > > > Having an explicit list of the build dependencies seems like the best > > way forward. > > I'm not a huge fan of this since we'd have to remember to update the > file each time deps change. Using the Ubuntu packaging deps seems more > pragmatic. Well, "apt-get build-dep" is great in theory, but it sounds like it may result in some dependencies coming from 12.04 and some from 14.04, because already-installed packages don't get updated, and according to Felipe, that already caused problems with autotools. What do you think would be the best way to solve this? -- Tanu
