Re: RFC: Reduce number of packages that are built for i686

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

 



Hi,

On 11/18/21 16:27, Fabio Valentini wrote:
> On Thu, Nov 18, 2021 at 1:14 PM Sérgio Basto <sergio@xxxxxxxxxx> wrote:
>>
>> Hi,
>> another subject that can be related
>>
>> In thread "I think we should stop building i686 packages we're not
>> shipping" we are alerted for builds for i686 that aren't publish .
>> Following the tip , I found some packages that we aren't shipped are
>> needed to allow mock start the buildroot for example tar-1.34-
>> 2.fc35.i686.rpm, tar is only available on koji local repo (1).
>>
>> I think we should have all i686 packages, that are needed to start a
>> buildrooot, published. i.e. available on x86_64 repos. To allow mock
>> build i686 packages without need to access to internal koji local repo
>> (which may not be public) .
> 
> This would break all sorts of things.
> 
> It's also not compatible with the current packaging guidelines,
> because packages must not conflict with each other unless they have an
> explicit Conflicts tag and a good reason to do so. in this case,
> tar.x86_64 and tar.i686 would conflict with each other (both providing
> /usr/bin/tar, among other files)

Ah, I see it has been so long ago since we made the switch that
some people no longer know the intricate details of how multilib
works :) Elf binaries are treated specially by rpm and are what
rpm calls colored IIRC. Not sure why it is called that, but the way
it works is that you can install both an i686 and x86_64 /usr/bin/tar
file with rpm and if you install i686 first then it will get replaced
with the x86_64 binary when you install that and if you install x86_64
first then that binary will stay in place (*).

This is done so that some package containing mainly a few .so.x libs
but also some small utils can be installed in multi-lib form without
need to split out the /usr/bin/utils into a separate package.

> so that's out of the question.

Not necessarily, note some files under e.g. /usr/share could still
conflict, but typically they do not.

Regards,

Hans



*) And I must admit I have no idea what happens if you remove the
x86_64 pkg while you still have the i686 pkg installed, maybe an
error ?

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [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