Handling package conflicts caused by arch specific doc files

[Reindl Harald]

Am 03.07.2014 13:20, schrieb Kalev Lember:
> On 07/03/2014 01:05 PM, Reindl Harald wrote:
>> /home/builduser/rpmbuild/RPMS:
>> total 44K
>> drwxr-xr-x 2 builduser builduser 4.0K 2014-06-30 17:09 noarch
>> drwxr-xr-x 2 builduser builduser  36K 2014-07-02 22:44 x86_64
> 
> Thanks, this actually backs up what I claimed -- that it's uncommon to
> build i686 packages on an x86_64 host. You only have an x86_64 directory
> here.

that is indeed true, a samll build-VM with only i686 is more
comfortable / less error prone than cross-building

> Out of curiosity, I know you are administering a number of systems -- do
> you only have x86_64 installations or do you use a different host for
> building i686 packages?

until 2011 i had a "buildserver32.vmware.local" to feed my notebook
with the exact same configuration and a sync-script, finally all
packages are grabbed from another host providing repos

now only x86_64 and luckily the "oldest" CPU to support is SandyBridge,
hence the 1:1 rebuilds of some packages which are not modified from the
src.rpm in /home/builduser/rpmbuild/rebuild

optflags: x86_64 -m64 -O2 -march=corei7-avx -mtune=corei7-avx -fopenmp -mmmx -msse2 -msse3 -msse4.1 -msse4.2 -mavx
-maes -mfpmath=sse -pipe -fomit-frame-pointer -finline-functions -finline-limit=60 -fexceptions
-fstack-protector-strong --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20140703/d8038033/attachment.sig>