Re: Re[4]: mmc patch

re: Did you do that mod_moto/0.18.0 version string in HTTP response
> header? I think this could be somehow connected (with CVS I mean).

yes ... this is what I'm doing now in src/mod/mod_moto.c and 
src/moto/main.c . I've checked in the past for good CVS vars I could 
sub in instead ... didn't find anything though . Although I can't say I 
looked that hard :)

-Dave

On Tuesday, January 28, 2003, at 01:27  PM, Cyb.org wrote:

> Hello David,
> Tuesday, January 28, 2003, 4:30:09 PM, you wrote:
>>> I suggest also:
>>>
>>>  -f            - force to overwrite if module exists in target place
>>>  -F            - don't overwrite if module exists in target place
>> Are both these options necessary or can we get by with only one of
>> them? I agree with Cory and Shay when the say 'the fewer switches the
>> better'. So in this case I think there is precedent for :
>> -f  - force to overwrite if module exists in target place
>> <default> - don't overwrite if module exists in target place
>> I would change mmc logic in the following way. If for some reason we
>> cannot write out the module to the destination location either because
>> it already exists there OR because we have no permission to write to
>> that location then /tmp/mmc-XXX should not be deleted and we should
>> output a message to that effect.
>
> This is what I wanted to hear (read). ;)
>
>>> Dave - do you know how to make $PROGVERSION variable in MMC right 
>>> from
>>> CVS version?
>> Umm ... I know how to get the build date in :) and currently the
>> version can be brought in from the configure script. I don't know how
>> to get it directly from cvs though. I'd sure like to find out! Having
>> the version strings in autoconf scripts just sucks.
>
> Did you do that mod_moto/0.18.0 version string in HTTP response
> header? I think this could be somehow connected (with CVS I mean).
>
> Cyb.org
>
>