GNOME nightly application ID 'Devel' suffix

Follow up to Why are there two Nautilus flatpak nightly packages?.

Appears we’re still using the old style Devel suffix (instead of preferred .Devel / .devel suffix) in App ID for the following nightly apps.

org.gnome.seahorse.ApplicationDevel
org.gnome.gitgDevel
org.gnome.font-viewerDevel
org.gnome.design.SymbolicPreviewDevel
org.gnome.design.IconLibraryDevel
org.gnome.design.AppIconPreviewDevel
org.gnome.clocksDevel
org.gnome.WeatherDevel
org.gnome.UsageDevel
org.gnome.TourDevel
org.gnome.SoundRecorderDevel
org.gnome.NautilusPreviewerDevel
org.gnome.NautilusDevel [✅]
org.gnome.MeldDevel [✅]
org.gnome.DejaDupDevel
org.gnome.CharactersDevel
org.gnome.BoxesDevel

Meld and Nautilus have both App IDs at the moment and the Devel suffix is planned for removal.

Also refer Application ID for Flatpak development.

I’m the author of org.gnome.DejaDupDevel from that list - and I don’t like the .Devel approach.

If memory serves, that recommendation of .Devel means that the two apps aren’t two separate namespaces, but rather some tools (like flatpak) treat .Devel as a sub-namespace of the normal app. I.e. the org.gnome.DejaDup flatpak app can talk to org.gnome.DejaDup.Devel over dbus without extra permissions and claim dbus names there, etc.

Not that it would intentionally, but it just feels like the wrong way to approach the problem - conceptually to me, I’d want to treat the two apps (stable and nightly) as entirely separate and distinct.

So for my part, the org.gnome.DejaDupDevel name is an intentional choice. Is there a particular advantage to the .Devel approach?

I think it’s cleaner to have app names separated from the Devel string using a '.' delimiter than appending to it.

Also, flatpak app and it’s nightly version are developed by the same developer / team, so I guess sub-namespace issue will never be encountered (though I understand your concern) ?

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.