https://bugzilla.novell.com/show_bug.cgi?id=636935 https://bugzilla.novell.com/show_bug.cgi?id=636935#c0 Summary: Naming convention for plugin/extension packages Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: vuntz@novell.com QAContact: qa@suse.de Found By: --- Blocker: --- We should make sure that all packages providing a plugin or extension follow a convention scheme. This is what I propose: <app-for-which-the-plugin-is>-plugin-<app-providing-plugin> For example, seahorse-plugins-gedit would be named gedit-plugin-seahorse since it contains a plugin for gedit that uses seahorse. If the application uses extensions instead of plugin, like nautilus, then we should use *-extension-*. For example: nautilus-extension-totem. Here's a list of apps providing a plugin/extension mechanism that we should check: eog evolution gedit gnome-bluetooth gstreamer inkscape nautilus nautilus-sendto pidgin tracker(?) Note: a similar case is panel applets. If a package provides an applet but the package itself is generally not about an applet, we should call the subpackage gnome-applet-<packagename> (or gnome-applets-<packagename> if there are more than one applet in the subpackage). For example, we should have gnome-applet-gdm. Note: it's unclear what we should do for browser plugins. For example: PackageKit-browser-plugin. Should it be called browser-plugin-PackageKit? Note: I'm wondering about libproxy. Not sure what's best there. Note: I'm wondering what to do about GIO modules (glib-networking and gvfs, mostly). Note: I'm wondering what to do about GTK+ modules. Is it worth it? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.