Re: libexec and multi-arch

On Sun, Feb 11, 2018 at 22:10:44 -0500, Jeff Johnson wrote: >> How is rpm recognizing files that are subject to this special-handling >> as same-path-executables? > > RPM reads elf headers and sets a per file color flag in metadata: > 0==no arch or not elf > 1==elf32 > 2==elf64 >

Re: libexec and multi-arch

On Sun, Feb 11, 2018 at 21:50:32 -0500, Jeff Johnson wrote: > And then there is the /usr/lib/rpm path to "probably argue" about. Not much to argue here until there are any _practical_ problems with this location. Although for the sake of good order you might consider using libexec here. > Truly

Re: libexec and multi-arch

> On Feb 5, 2018, at 5:46 PM, Tomasz Pala wrote: > > On Mon, Feb 05, 2018 at 15:20:55 -0500, Jeff Johnson wrote: > >>> No, it only hidden the problem behind getconf binary being handled >>> _somehow_. I once even wondered how this is done, apparently rpm is >>> trying to be

Re: libexec and multi-arch

> On Feb 5, 2018, at 3:23 PM, Neal Gompa wrote: > > I'd probably argue that libexec should have the same multi-arch > handling that (s)bin does (primary arch "wins" and secondary arches > are ignored), though last I checked this isn't specific to paths and > should Just