Re: Handling package conflicts caused by arch specific doc files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

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.

-- 
Hope this helps,
Kalev
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux