Re: Multiarch file overlap summary and proposal

2012-02-16 Thread Russ Allbery
I was thinking more about this, and I was finally able to put a finger on why I don't like package splitting as a solution. We know from prior experience with splitting packages for large arch-independent data that one of the more common mistakes that we'll make is to move the wrong files: to put

Re: Multiarch file overlap summary and proposal

2012-02-16 Thread Carsten Hey
* David Kalnischkies [2012-02-16 03:59 +0100]: > On Thu, Feb 16, 2012 at 00:39, Russ Allbery wrote: > >>>   it needs to find and remove foo:* foo:all (or foo:any) instead of foo:* would save the need to quote it. > > Actually, why would that be the behavior?  Why would dpkg --purge foo not > > j

Re: Multiarch file overlap summary and proposal

2012-02-16 Thread Carsten Hey
* Russ Allbery [2012-02-16 10:43 -0800]: > * Users who want to co-install separate architectures will immediately > encounter a dpkg error saying that the files aren't consistent. This > means they won't be able to co-install the packages, but dpkg will > prevent any actual harm from happeni

Re: Multiarch file overlap summary and proposal

2012-02-16 Thread Russ Allbery
Carsten Hey writes: > * Russ Allbery [2012-02-16 10:43 -0800]: >> * Users who want to co-install separate architectures will immediately >> encounter a dpkg error saying that the files aren't consistent. This >> means they won't be able to co-install the packages, but dpkg will >> prevent