Stephen Gran wrote: > This one time, at band camp, Michael Tautschnig said: >> There is just a slightly archive-specific problem: A package in main >> must not depend on something outside main (at least so I guess, I >> couldn't find the docs stating this rightaway). We'd thus need some >> clamav package in main, and not only in volatile. Which more or less >> is the situation we have today. > > A way around this problem might be to integrate volatile slightly more > with the main dak archive. Treating volatile (from the point of view > of dak) as a kind of proposed-updates queue (that may or may not get > rolled into stable point releases) would allow us to have packages in > main depend on packages in main/volatile (I think - ICBW).
As what you call main/volatile is not in stable, I don't think that's a solution. The oposite would work though: packages in volatile depending on packages in stable (like with proposed-updates...). Cheers Luk -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
