Re: taking dependencies

[Laurent Martelli <laurent@bearteam.org>]

>>>>> "Sven" == Sven  <luther@dpt-info.u-strasbg.fr> writes:

  Sven> On Mon, Mar 11, 2002 at 11:46:15AM +0100, Benjamin Drieu
  Sven> wrote:
  >> pp <pp@infoglob.com> writes:
  >> 
  >> > Is there any (I do not say easy) way > to automagically take
  >> dependencies from configure > script and place it in control
  >> files?
  >> 
  >> I'm not aware of any automagic way to catch source dependencies,
  >> although shared libraries dependencies can semi-automatically be
  >> found (i.e. with dh_shlibdeps).

  Sven> You could use a trick similar of what is done with fakeroot
  Sven> (or even patch fakeroot if you use that to build your
  Sven> packages) to simply log to an external file every read access
  Sven> you do. Later you only need to go trough this list of files,
  Sven> have dpkg -S run on them to check to which package they
  Sven> belong, and then sort them a little, eliminate duplicates,
  Sven> eliminate files belonging to build essentials, and you will
  Sven> obtain automatic build dependencies.

I think that strace could be used to know which files are read from.

-- 
Laurent Martelli
laurent@bearteam.org              http://www.bearteam.org/~laurent/