Ximin Luo:
> Mike Frysinger:
>> On 28 Jul 2016 15:15, Florian Weimer wrote:
>>> On 03/09/2016 05:30 PM, Mike Frysinger wrote:
would it be so terrible to properly marshall this data ?
>>>
>>> Ximin Luo and I discussed this and I wonder if it is possible to read
>>> out the libc.so.6 build ID i
Mike Frysinger:
> On 28 Jul 2016 15:15, Florian Weimer wrote:
>> On 03/09/2016 05:30 PM, Mike Frysinger wrote:
>>> would it be so terrible to properly marshall this data ?
>>
>> Ximin Luo and I discussed this and I wonder if it is possible to read
>> out the libc.so.6 build ID if it is present. I
On 28 Jul 2016 15:15, Florian Weimer wrote:
> On 03/09/2016 05:30 PM, Mike Frysinger wrote:
> > would it be so terrible to properly marshall this data ?
>
> Ximin Luo and I discussed this and I wonder if it is possible to read
> out the libc.so.6 build ID if it is present. It should indirectly c
Florian Weimer skribis:
> We still need the time-based approach if the build ID is not
> available, but I expect most distributions will have something like
> it.
FWIW in Guix we solve it by filling the ‘compilation’ array with a
substring of the installation prefix¹.
Since the installation pre
On 03/09/2016 05:30 PM, Mike Frysinger wrote:
would it be so terrible to properly marshall this data ?
Ximin Luo and I discussed this and I wonder if it is possible to read
out the libc.so.6 build ID if it is present. It should indirectly call
all the layout dependencies and be reasonably e
5 matches
Mail list logo