Re: Stable code with unstable dependancies.

Cipriano Groenendal wrote:

Hello list. [snip]

Should something be done about packages like this? IMHO the installer should, with preferred-state set to stable only download stable packages, unless it's -forced. Even better would be if packages depending upon something unstable could never reach the Stable condition unless all its dependencies would be. The same requirements could be made for the Alpha/Beta/Devel levels of stability.

I think the requirement for "stable" makes perfect sense - any stable package must not have a required dependency on a less-than-stable package. Optional dependencies are always of course allowed, as Alan has fixed in DB_DataObject. The installer should in fact always honor the preferred state, and it currently isn't in every case, something the core devs are trying to track down. Regards, Greg