Re: low-priority ups bug: build date
Tom Hughes <[email protected]> Tue, 30 Nov 2004 22:45:48 GMT
| Newsgroups | gmane.comp.debugging.ups.user |
|---|---|
| Message-ID | <[email protected]> |
In message <1101850268.4744.87.camel@wdowlingpc>
"William F. Dowling" <[email protected]> wrote:
> When I did this with my freshly-built-from-CVS-source ups:
> $ ups -v
> I was surprised to see
> ups version 3.38beta1-cvs (build date: Fri Oct 25 16:57:55 BST 2002)
>
> I thought my install was bad and I was getting an old build somehow.
> Actually, this string is hard-coded in the source:
>
> $ grep 'build date: ' ups/*.[ch]
> ups/sccsdata.c: "ups version 3.38beta1-cvs (build date: Fri Oct 25
> 16:57:55 BST 2002)",
>
> An sccsdata.c file appears in several directories. I guess the "build
> date" should be computed and stuffed in there during the make process.
I have no idea how that gets built. It looks like it is some horrible
throwback to when the code was held in SCCS or something. I think the
sccsfile target tries to update it but it uses an sccsinfo command
which I don't have, and which presumably wouldn't work anyway.
> BTW, what is the best way to report things like this?
> [email protected]? sourceforge? Direct to you/ianedwards?
> In general I don't like to spam developers especially with little stuff,
> but I don't want to send a report someplace it will get lost.
Well there should be a bug tracker on sourceforge I guess although
we've never used it much so far. Either that or on the list I guess.
Tom
--
Tom Hughes ([email protected])
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/