bug#28167: decide how to deal with gschemas

bug#28167: decide how to deal with gschemas

[ng0]

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

Creating manual page database for 59 packages... done in 2.152 s
warning: collision encountered: /gnu/store/7dq7vkvrykv3wm9l8j617v3xbn44g51i-epiphany-3.24.3/share/glib-2.0/schemas/gschemas.compiled /gnu/store/1c7w0pjf80z8l6yb9a8wmni8za3mpx85-simple-scan-3.24.1/share/glib-2.0/schemas/gschemas.compiled
warning: arbitrarily choosing /gnu/store/7dq7vkvrykv3wm9l8j617v3xbn44g51i-epiphany-3.24.3/share/glib-2.0/schemas/gschemas.compiled

1.
How do we deal with these gschema collisions? I know eventually we
should solve almost all collisions we have, but gschemas seems
more important than the usual ones.

2.
I also think we should formalize how to deal with the collisions
or specific groups of collisions, so that we might have a better
way to tackle these issues.
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

bug#28167: decide how to deal with gschemas

[Ricardo Wurmus]

ng0 <ng0@infotropique.org> writes:

> Creating manual page database for 59 packages... done in 2.152 s
> warning: collision encountered: /gnu/store/7dq7vkvrykv3wm9l8j617v3xbn44g51i-epiphany-3.24.3/share/glib-2.0/schemas/gschemas.compiled /gnu/store/1c7w0pjf80z8l6yb9a8wmni8za3mpx85-simple-scan-3.24.1/share/glib-2.0/schemas/gschemas.compiled
> warning: arbitrarily choosing /gnu/store/7dq7vkvrykv3wm9l8j617v3xbn44g51i-epiphany-3.24.3/share/glib-2.0/schemas/gschemas.compiled
>
> 1.
> How do we deal with these gschema collisions? I know eventually we
> should solve almost all collisions we have, but gschemas seems
> more important than the usual ones.

For reference, here’s the discussion of the same issue by the Nix folks:

  https://github.com/NixOS/nixpkgs/issues/1455

> 2.
> I also think we should formalize how to deal with the collisions
> or specific groups of collisions, so that we might have a better
> way to tackle these issues.

I don’t know what “formalize” means in this context, but I agree that we
should aim to reduce the number of conflicts where possible.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net