Re: Build-Depends
Jules Bean schrieb:
> On Fri, Feb 23, 2001 at 05:46:00AM +0100, Bernd Eckenfels wrote:
> > Well, one thing is to look at the runtime libs which are required. You most
> > likely need the runtime libs packages for all your -dev dependencies. In
> > addition you can log the file opens (strace) while you build. And then
> > search all those files in the package list. Actually this sounds like a good
> > idea. Perhaps fakeroots lib has some support for that? I think there are
> > some "make install" watchers out there which trap writing, so reading should
> > be done as easyly.
> A script to run build under strace -e trace=file and then use dpkg -S
> to find the files would also work; I think it's pretty slow, and I'm
> sure I remember another disadvantage (but I can't remember it). Maybe
> someone would like to hack something together.
[ dont take this too seriously ]
Probably adding another layer of storage (the network) to the
virtual memory system, from which stuff is pulled to the next
faster layer (the harddisk) whenever something is needed for the
first time and not already present there would be the most
general approach to this.
It would look as if you had everything installed, though most
files are not locally installed but "swapped" out to the
network. Dealing with conflicts would be difficoult I imagine.
Hmm, does CODA work like this? This would give us a _real_
network OS ...
ciao, 2ri, desperately in need for a coffee
--
All constants are variables.
Reply to: