Hi Abou,

On 19-10-2019 16:05, Abou Al Montacir wrote:
> More analysis of the issue showed that we want the lpk file containĀ 
> 
> <AutoUpdate Value="Manually"/>
> 
> when the lazarus-src package is not installed, but we probably want to have
> 
> <AutoUpdate Value="AsNeeded"/>
> 
> when lazarus-src is installed.

Ack.

> So one solution is to package both file versions and used dpkg-divert to
> override lcl-units lpk files by those of lazarus-src when installed.

Uch, I'm not overly enthusiastic about this solution. I guess it's
mostly unexpected by Debian users that the same file can have different
content depending on which package set is installed. But, as you already
implemented it, let's see how it goes.

> The other option is that that post install script of lazarus-src looks
> for the installed lpk-files and modifies them, but this is probably an
> unwanted behavior, especially that some lcl-units may be installed after
> lazarus-src installation.

And that's even less pretty. I'm glad you didn't choose this option.

> Any other idea?

If this is the way Lazarus works, I think it's best to just depend on
lazarus-src. That ain't pretty, but it's at least consistent with how
people expect Debian to install files.

Paul

By the way, I think the postinst and preinst shouldn't have been
committed to git, right? They're generated during package build.


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to