On Wednesday, 3 January 2024 10:07:02 IST Marián Konček wrote:
> Note that mingw-* packages currently in Fedora install into the 
> /usr/i686-w64-mingw32/ or /usr/x86_64-w64-mingw32/ directories.
> 
> This is a different topic but if each archful package installed its 
> files into a directory containing the arch name, it would allow parallel 
> installability without configuring dnf and possibly make it more 
> convenient for cross-platform development.

This is very similar to Debian's Multiarch[1], but they have 
/usr/lib/<arch-tuple> (less pollution of top-level /usr)
Indeed, such organization is ideal for cross-platform development:
     *  Libraries are installed in the same path, both for native and for cross 
compilation
     *  As a result, normal packages in the distribution already have the 
libraries in the correct locations for both native/cross compilation
     *  The packaging system (APT) was adapted to allow co-installation of such 
packages (since the files don't conflict)
     *  At a later stage, the distribution began shipping complete toolchains 
for all supported architectures -- built from exactly the same source (same 
gcc, same binutils, etc.)
     *  I.e: a developer that need cross-compilation, install the wanted 
toolchain(s) and all library packages are immediately available from standard 
repositories.

I guess Fedora people that work on ARM/ARM64/RISC-V would love such a support.

Bye,

--
Oron Peled

> On 2. 1. 2024 16:23, Vít Ondruch wrote:
> >
> >
> > Dne 02. 01. 24 v 13:42 Stephen Smoogen napsal(a):
> >>
> >>
> >> On Tue, 2 Jan 2024 at 06:21, Vít Ondruch <vondr...@redhat.com> wrote:
> >>
> >>
> >>     Dne 28. 12. 23 v 17:12 Aoife Moloney napsal(a):
> >>>     The dynamic linker already has the `glibc-hwcaps` mechanism to load
> >>>     optimized implementations of ''shared objects'' [3]. This means that
> >>>     packages can provide optimized libraries and they linker will be
> >>>     automatically load them from separate directories if appropriate.
> >>>     (For AMD64, this is `/usr/lib64/glibc-hwcaps/x86-64-v{2,3,4}/`.)
> >>>
> >>
> >>     Is this something specific to x86_64 that the libs needs to be
> >>     nested in a place such as
> >>     `/usr/lib64/glibc-hwcaps/x86-64-v{2,3,4}/`? Why not use e.g.
> >>     `/usr/x86-64-v{2,3,4}/lib` directories instead? Or something more
> >>     universal.
> >>
> >>
> >> Adding directories to the /usr sub-space generally gets bogged down 
> >> into 'You are polluting my name-space' arguments which get no-where 
> >> because some of the people getting angry is having to live with some 
> >> 3rd party rules and regulations which stipulated how things look and 
> >> will only get updated once a decade or so. [The same goes with 
> >> subdirectories in /usr/bin etc where it causes similar problems.] 
> >> There tends to be no 'general' case which works unless it gets 
> >> 'agreed' upon by some outside of the distro body that publishes 
> >> 'versioned' standards.
> >
> >
> > Checking what Debian does, they have paths such as 
> > `/usr/lib/x86_64-linux-gnu/`. So we would not be alone.
> >
> >
> > Vít
> >
> >
> >>     Vít
> >>
> >>     --
> >>     _______________________________________________
> >>     devel mailing list -- devel@lists.fedoraproject.org
> >>     To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> >>     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@lists.fedoraproject.org
> >>     Do not reply to spam, report it:
> >>     https://pagure.io/fedora-infrastructure/new_issue
> >>
> >>
> >>
> >>
> >> --
> >> _______________________________________________
> >> devel mailing list --devel@lists.fedoraproject.org
> >> To unsubscribe send an email todevel-le...@lists.fedoraproject.org
> >> 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@lists.fedoraproject.org
> >> Do not reply to spam, report 
> >> it:https://pagure.io/fedora-infrastructure/new_issue
> >
> > --
> > _______________________________________________
> > devel mailing list --devel@lists.fedoraproject.org
> > To unsubscribe send an email todevel-le...@lists.fedoraproject.org
> > 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@lists.fedoraproject.org
> > Do not reply to spam, report 
> > it:https://pagure.io/fedora-infrastructure/new_issue
> 
> 


-- 
Oron Peled                                 Voice: +972-4-8228492

Unsolicited commercial email read for $500 per message.


--------
[1] https://wiki.debian.org/Multiarch
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to