Handling package conflicts caused by arch specific doc files

[drago01]

On Wed, Jul 2, 2014 at 5:01 PM, Kalev Lember <kalevlember at gmail.com> wrote:
> On 07/02/2014 03:15 PM, Ankur Sinha wrote:
>> I was wondering if there's a standard way of solving package conflicts
>> that arise from arch specific doc files. An example is here:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=565676
>>
>> The conflict is because the docs are generated during the build, and the
>> files, even though they are installed in the same location, differ.
>
> My personal take on this is that multilibbed -devel packages are rarely
> tested and largely useless. Most people use mock (or some other chroot
> mechanism or a VM) for building 32 bit packages on 64 bit hosts instead.

Where is the data that backs up the "most people" claim. -devel
packages are also
used to build stuff locally there are not only for rpms (and even in
the rpm case
using local builds is way more convient then using mock or even a VM *sigh*).

> Multilibbing libs makes a lot of sense, but -devel packages, not so
> much. I wonder how many users would miss this if we were to blacklist
> all -devel packages in mash.
>
> Anyway, having said that, I've hopefully now fixed it in
> libchamplain-0.12.8-1.fc21 build.

That's what we should do ... fix bugs and not just use the big hammer
because some package had a bug.