Re: Upload libloc to Debian

[Michael Tremer <michael.tremer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 2473 bytes --]

Hello Jochen,

Wow. I am impressed how quick you are. That is the spirit!

Thank you so much!

> On 7 Jul 2022, at 07:46, Jochen Sprickerhof <libloc(a)jochen.sprickerhof.de> wrote:
> 
> * Michael Tremer <michael.tremer(a)ipfire.org> [2022-07-06 09:29]:
>> This is what I expected. However, if —-verify complains, shouldn’t it complain about the symlink, too?
> 
> No, I create the symlink in the maintainer scripts:
> https://salsa.debian.org/debian/libloc/-/blob/master/debian/location.postinst
> https://salsa.debian.org/debian/libloc/-/blob/master/debian/location.postrm

Ah, that is something I didn’t think of :)

>> Yes, I wouldn’t want any discrepancies here and be as consistent as possible.
>> 
>> So, would you be up for submitting a patch for this as well?
> 
> Attached.

I merged this patch and the one from your previous email into master.

I didn’t rebuild the packages, yet, as there is probably no need.

>> Ultimately, I am not even sure if there is any point in keeping those build scripts around in our repository. There should only be one set of packages available and if that is part of the distribution already, I do not see any reason why we should have our own set of packages, too.
> 
> Agreed, though I will upload the package to Debian unstable from where it will transition to testing to be part of the next Debian version (bookworm). You probably want to provide packages for the older Debian versions, still.

Yes, at least we need to support stable at the moment to make it easier to use libloc.

But that creates a couple of problems for us:

I don’t really want to provide packages for unstable and bookworm then, because should use the “official” packages.

But I do want to be absolutely compatible with unstable. See below...

> I've uploaded first versions here:
> 
> https://salsa.debian.org/debian/libloc
> https://salsa.debian.org/debian/libloc-database
> 
> Note that these target Debian unstable and will probably not build on older Debian versions. Testing and comments welcome.

And that is the problem then…

Would it be a good idea to merge all your changes into our Git repository? Is it long term a good idea to keep debian/ in our repository? In theory that could go as soon as bookworm becomes stable.

Any pointers what would be a good idea to do here?

-Michael

> 
> Cheers Jochen
> <0001-Merge-location-importer-into-location-package.patch>