You are not logged in.
Every combination seems to be in use already...
VIM plug-ins are vim-plugin_name
XFCE plug-ins are xfce4-plugin_name-plugin
GIMP plug-ins are (mostly) gimp-plugin-plugin_name
I plan on making some plug-in packages for a application what dose not currently have any available. So as the topic says what's preferred package naming convention? I personally like the GIMP format best but just figured I'd ask first (should really be in the guidelines IMO).
Offline
Offline
I also vote on using the third option, it seems the clearest too me.
PC: Antec P182B | Asus P8Z77-V PRO | Intel i5 3570k | 16GB DDR3 | GeForce 450GTS | 4TB HDD | Pioneer BDR-207D | Asus Xonar DX | Altec Lansing CS21 | Eizo EV2736W-BK | Arch Linux x86_64
HTPC: Antec NSK2480 | ASUS M3A78-EM (AMD 780G) | AMD Athlon X3 425 | 8GB DDR2 | GeForce G210 | 2TB HDD | Arch Linux x86_64
Server: Raspberry Pi (model B) | 512MB RAM | 750GB HDD | Arch Linux ARM
Offline
Ok well I guess I'll use the third option for now them.
While we're talking about naming conventions I was just searching for the python cairo library noticed binding library's could do with some guidance to...
cairo-perl
pycairo
ruby-rcairo
IMO language-library_name would be a nice guideline.
Offline
Very good points N3ON, completely agree.
Offline
*raises hand in assention with previous posters opinions*
Offline
While in a few cases there have been specific guidelines made for plugin/module naming, in general the format followed upstream is used. As long as it is consistent within a package group, then it really does not matter that much.
Offline