[Piuparts-devel] Bug#850917: Please export /var/lib/dpkg/alternatives content after installation

[Michael Stapelberg]

Thinking some more about it, I think it would be good to export not
only the alternatives _after_ package installation, but before _and_
after package installation. That way, consumers can compare the
differences which the package caused, or look at the end result,
whichever fits their use case best. For manpages.debian.org, I’m
currently thinking we’d need the diff for a clean implementation.

I’m expecting you have further comments about the patch anyway :).

On Wed, Jan 11, 2017 at 2:34 PM, Michael Stapelberg
<stapelberg at debian.org> wrote:
> On Wed, Jan 11, 2017 at 12:55 PM, Andreas Beckmann <anbe at debian.org> wrote:
>> On 2017-01-11 12:44, Michael Stapelberg wrote:
>>> Thanks for the suggestion. I considered this, but I’m worried this
>>> might blow up the logfiles quite a bit for some packages.
>>
>> How much "logfile" data would that be? Installing texlive-full in sid
>> with --install-recommends produces 460 kb, distupgrading it from stable
>> (without recommends) 700 kb, and there are some packages producing more
>> output than that.
>
> I don’t expect the output to be more than a few kilobytes, so size is
> probably indeed not a concern. Making the files available under a
> clean URL that is independent of the test result remains a concern of
> mine, though.
>
> Attached you can find a first stab at implementing this feature. I
> introduced a new protocol message to transfer base64-encoded arbitrary
> binary data. This can easily be used to transfer other files in the
> same spirit, should that become necessary in the future (it also seems
> like the clean thing to do, even if we’re just talking about a single
> file). The files are then made available at
> /<section>/aux/<package>_<version>/<filename>, e.g.
> /sid/aux/libva1_1.7.3-2/alternatives.tar.gz.
>
> Looking forward to your feedback,
>
> --
> Best regards,
> Michael



-- 
Best regards,
Michael