On Jul 14, 2007, at 3:51 PM, Guenter Knauf wrote:

> Hi all,
> I want to suggest this (shamlessly stolen from libcurl, hehe):
>
> --- libssh2.h.orig    Tue Jul 10 00:47:32 2007
> +++ libssh2.h Sat Jul 14 21:44:32 2007
> @@ -79,7 +79,31 @@
>  typedef long long libssh2_int64_t;
>  #endif
>
> --- libssh2.h.orig    Sat Jul 14 21:53:48 2007
> +++ libssh2.h Sat Jul 14 21:48:18 2007
> @@ -79,7 +79,31 @@
>  typedef long long libssh2_int64_t;
>  #endif
>
> -#define LIBSSH2_VERSION                             "0.16-CVS"
> +#define LIBSSH2_VERSION                             "0.16.0-CVS"
> +
> +/* The numeric version number is also available "in parts" by  
> using these
> +   defines: */
> +#define LIBSSH2_VERSION_MAJOR                       0
> +#define LIBSSH2_VERSION_MINOR                       16
> +#define LIBSSH2_VERSION_PATCH                       0
> +
> +/* This is the numeric version of the libssh2 version number,  
> meant for easier
> +   parsing and comparions by programs. The LIBSSH2_VERSION_NUM  
> define will
> +   always follow this syntax:
> +
> +         0xXXYYZZ
> +
> +   Where XX, YY and ZZ are the main version, release and patch  
> numbers in
> +   hexadecimal (using 8 bits each). All three numbers are always  
> represented
> +   using two digits.  1.2 would appear as "0x010200" while version  
> 9.11.7
> +   appears as "0x090b07".
> +
> +   This 6-digit (24 bits) hexadecimal number does not show pre- 
> release number,
> +   and it is always a greater number in a more recent release. It  
> makes
> +   comparisons with greater than and less than work.
> +*/
> +#define LIBSSH2_VERSION_NUM 0x001000
> +
>  #define LIBSSH2_APINO                               200706151200L
>
>  /* Part of every banner, user specified or not */
>
> comments?

That sounds like a good solution.

Jim

--

/"\   ASCII Ribbon Campaign  .
\ / - NO HTML/RTF in e-mail  .
  X  - NO Word docs in e-mail .
/ \ -----------------------------------------------------------------
                      http://www.FreeBSD.org     The Power to Serve
[EMAIL PROTECTED]  http://www.TheHousleys.net
---------------------------------------------------------------------
Q: Because it reverses the logical flow of conversation.
A: Why is putting a reply at the top of the message frowned upon?



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
libssh2-devel mailing list
libssh2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libssh2-devel

Reply via email to