Yo folks,

I would like to propose that we agree on a consistent naming convention for SSL variants of package. Let me show you an example to explain what I mean:

lftp-ssl.info:Description: Sophisticated command line based FTP client (SSL)
lynx-ssl-2.8.4-13.info:Description: Console based web browser (SSL-enabled)
net-snmp-ssl.info:Description: SNMP tools and libraries (OpenSSL enabled)
openslp-ssl-1.0.9a-1.info:Description: Open Service Location Protocol (OpenSLP), SSL enabled
openslp-ssl-1.0.9a-1.info: Description: Shared Libraries for OpenSLP + SSL Support
postgresql-ssl-python.info:Description: PostgreSQL Python support (with SSL)
postgresql-ssl-tcl-7.2.3-3.info:Description: PostgreSQL TCL tools (with SSL support)
python23-socket-ssl-2.3.1-11.info:Description: Socket plugin for python (SSL version)
uw-imap-c-client-ssl.info:Description: UW IMAP C-Client Library *SSL VERSION*
wget-ssl-1.8.2-2.info:Description: Automatic web site retreiver, with SSL support




That's 10 different ways to say one and the same thing. Not a big problem. but I'd prefer if we could agree on a consistent scheme anyway: Consistency helps users, and it's rather to achieve for us (at least for 95% of the package; it will happen again in the future that people checking package which are not consistent with the rules, just like again and again package which do not validate warning-free get checked in; but that's something we can cope with).

So, my question is, which one to pick. Personally, I prefer to put the "optional" stuff into parentheses. Also brevity is a boon. So I suggest the suffix "(with SSL)".

Opinions? Comments?

Cheers,

Max



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to