Re: large number of source package version problems in the archive

[luther@maxime.u-strasbg.fr]

Hello,

I was thinking that it would be nice to have, not only packages dependencies, but also some source code needed to build dependencies, this way it would be easier to check that the correct source is still available, also that would permit someone to check  that he has all needed packages installed to build the package. (and not after 3 hours of compile :)).

we could have a virtual compiler environment package that contains all standard developpment tools (make gcc, etc...) and then a list of additional packages, or conflictiong packages from the previously listed (like don't work with gcc, use egcs or somethink like that), or gcc is not needed.

that could be more than one such base developpment virtual packages, one for compiled packages, one for scripts and such, one for documentation, etc ...

does this make sense ?

Friendly,

Sven LUTHER