-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22.02.2016 03:45, Neal Gompa wrote:
> On Fri, Feb 12, 2016 at 6:42 PM, Kamil Rytarowski
> wrote:
>>
>> Thanks!
>>
>> I somehow lost interest since --chroot cannot be implemented
>> with rpm(1) on NetBSD with chroot(2). There is not known a
>> b
On Fri, Feb 12, 2016 at 6:42 PM, Kamil Rytarowski wrote:
>
> Thanks!
>
> I somehow lost interest since --chroot cannot be implemented with
> rpm(1) on NetBSD with chroot(2). There is not known a breakage from
> NetBSD chroot.
Kamil,
Two things:
* Doesn't --root already use chroot(2)? Also, as fa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11.02.2016 14:51, Florian Festi wrote:
> Looks like this fell through the cracks back then. I can only guess
> why. May be everyone was on vacation...
>
> Anyway this topic came up recently and this looks like the proper
> solution. Pushed upstr
Looks like this fell through the cracks back then. I can only guess why.
May be everyone was on vacation...
Anyway this topic came up recently and this looks like the proper
solution. Pushed upstream as 61109446ac67ca8f3d96a5592814561db908d83c
with only very minor corrections as followup patches.
Hello,
I'm attaching a big patch refactoring deeply the current setprogname() and
getprogname() feature.
Change-log explains everything:
The RPM code contains setprogname()/getprogname() support implemented through
compatiblity layer with very old GLIBC (internals supported back to '95 and
ea
