Roman Hodek wrote: > The prefix idea is good, here a suggestion for concrete syntax:
I´d prefer a syntax in the style of /etc/exports, e.g. Build-Depends: package1, package2(CPU1), package3(!CPU1), package4(SYSTEM2-CPU2, SYSTEM3-*), package5 | package6(CPU1), package7(CPU1, >= 2.0), package7(!CPU1, >= 2.1) It looks a bit easier to read (and create) to me than the prefix syntax as there is already a colon after "Build-Depends". If there is a system-cpu specification, it must be before the version specification, so a parser for this would not be too difficult. About the conflict headers: I don´t think they are necessary, so I vote for removing them from the proposal (as Richard suggested). About 4 or 6 fields (actually 2 or 3 without *-Conflicts:): Both models are fine for me, I prefer the one with 3 fields. -- Stefan Gybas
