On 11/11/10 17:42, Peter Simons wrote:
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". As you no doubt know there are tools that help with satisfying dependencies at build/install time. However, there is a lack of tools to make sure that the dependencies stay satisfies. I'm surprised you haven't bumped into this yourself actually. http://therning.org/magnus/archives/751 /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe