On Fri, Jul 24, 2009 at 12:30 PM, Ramsay Jones<ramsay@xxxxxxxxxxxxxxxxxxx> wrote: > $ git checkout master > $ git describe > 0.4.1-99-g37f041a If works well if you are following the official branch. If you are working on your own, you might have some private tag. Then that will mess up the "git describe". My tag might not even look like a version number. So for version numbers, I still prefer the dot and numbers. We can follow what Linux kernel do for version strings. > My intent with this patch was to provide sparse (the program) with a > version number; *not* the sparse library, which is a separate issue. > (If a library version number is implemented, then the sparse program > version number *could* be the same number, of course). I did not > consider the other example programs built with sparse, but I suppose > they could all share the same version number if necessary. In my mind, they share the same version number. Individual version the program inside sparse package is kind of messy. I don't see a need for that in the near future yet. > However, you would not want sparse (the library) to force *all* > applications built with the library to handle the --version option > by printing the sparse (the program) version string and exiting! That is what YOUR current patch do, no? > > So, the library should just set a version_option seen flag and let > the application process this flag itself. That will force every program to process the version itself, doing more or less the same thing. Let's say I don't need separate version inside sparse package. Does "-v" printing out sparse version string in side lib.c satisfy your need already? In that case, I don't see the need for a separate "--version". Chris -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
