Hi Magnus,
AFAICS there are roughly two sides to consider. Packages delivered in binary format, and packages delivered in source format (AUR).
Binary: The burden falls on the developers who provide the binary packages to make sure that all binary packages are mutually compatible.
Source: The burden falls on the user to make sure that his system is sane.
wait a second, let me get this straight. In case of AUR, the *user* has to figure out how to satisfy a package's dependencies? That is our policy?
It depends what you mean by "satisfy a package's dependencies".
I was trying to clarify your statement that "The burden falls on the user to make sure that his system is sane." You said that in the context of source packages, like AUR, contrasting the situation with a binary repository where "The burden falls on the developers who provide the binary packages to make sure that all binary packages are mutually compatible." So, I guess you were saying that we ("developers") do *not* have to care whether the packages we upload to AUR are mutually compatible, because that's the users problem. Did I understand that right? Take care, Peter