Re: Poor man's "source dependencies"

[Sven LUTHER <luther@maxime.u-strasbg.fr>]

On Sat, Mar 06, 1999 at 12:19:13AM -0600, David Welton wrote:
> Sort of a vague idea popped into my head.  Don't know if it's already
> been considered and rejected or anything, but...:
> 
> Would it be easier to just find the list of packages necessary to
> build everything, and say 'ok, this is the list you need for a build
> system'.  That wouldn't be terribly useful for recreating a 'make
> world', but at least it would let the ports people know what to shoot
> for...  Unless it were too big a list...
> 

A nice thing would be to have a "comon developpment stuff" group of packages,
and that developpers could build a system with that system, and add any stuff
that are needed to that list.

Another solution, would be to run dpkg-buildpackage stuff trough a filter who
would list any file, except those from in the current idr or any subdir, used
in the compile in a separate file, and at the end of the compilation, do a dpkg
-S of the files and put them in a field of the control field.

If you don't want it in a control field because dpkg or something weill not
know about it, at least you could put it in a Porting file in the debian
subdir, or something like that, so that we porter could check it if needed ...

note that this would call for building the source package at the end of
compilation or something such. or can you append stuff to a diff easily ?

i don't know so much about this stuff, but i would be willing (as time
permits) to work on it, if someone can give me any hint on how to catch all
files used by the build process.

i guess you could call a bash wrapper, that will just log any file system
access, a bit in the way the script does it, or some magic in the way of sudo
or fakeroot ?

Any idea on this ?

Friendly,

Sven LUTHER