> *Parts*, fine, I have no problem with parts. I was just a little > croggled by the example of trying to autogenerate *all* source > dependencies for the debian-policy package.
The automatically generated parts will be only -dev packages for shared libs. > I think it may turn out to be more hairy than we think. For example, > many packages will require awk to build. Ok, but we have several awk > packages -- which one will the source-depends use? Awk is a virtual > package -- is this source-dependency-building tool going to figure > that out? First: you can perfectly well source-depend on a virtual package. Second: awk won't be in the list that is automatically constructed. Ok, there could be a tool (libtricks-based) that helps you constructing the non-auto-generated parts, but in this case still a human has the last decision. So virtual packages aren't a problem for this. Roman
