On 04 Sep 2002 19:10:34 +0200, Dominik Vogt wrote: > > I understand your point. My point is: > > * Nobody except the developers should run fvwm-themes against > CVS. And I guess it isn't hard to chop off the suffix from the > version number in cvs.
It is possible to "correct" the version string once the rules are known. > * Nobody should build a tarball or rpm from CVS except for > testing if the tarball builds. We discuss this only because someone do want to build daily rpms. After all, I implemented "make rpm", so anyone may build an rpm from any source (including snapshot and cvs) and install it on several machines. Here it is possible to patch the "make rpm" procedure as well, but then the resulting rpms will have another version than the source tarballs, I would like to solve it more directly. > * I don't want to see "I have x.y.z" ever again when the user has > the cvs sources. > > See the list above. These are all places where a user might look > to find out the release number and should all print "cvs" or > whatever as part of the version string. I mean, in a way that the > user concludes that it's part of the version name. I don't think in the past we had many users that did not mention they use a snapshot or cvs. For me, it is not a requirement to always feed "cvs" to a user. It is more important to make all possible automatical tools happy. Also, saying "I use 2.5.4_cvs" does not help much. Saying "I use fvwm-snap-20020904.tar.gz" or "I use 2.5.4 (from cvs 2002-09-04)" helps. > I'd rather make some effort to filter out the suffix for tools > that can't handle it, but I'm open to a different solution that > achieve the same. A human readable suffix is fine, but I guess > > "2.5.4 (cvs)" > > would be reported as "2.5.4". I will implement my solution (something in the middle) and if you don't like it, just restore the current one or the old one, whatever you decide. Hopefully we will not need to return to this discussion again. Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
