|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
|
|
VERSION->rev and SVN versionI just updated to SVN 6393 but my deamon is still saying 6377. This needs to track the the SVN or at least the lastest .c/.h file in SVN?
$ svn update At revision 6393. "rev":"$Id: gpsd_json.c 6377 2009-10-01 23:24:21Z esr $" $ svn update U www/AIVDM.txt U www/hacking.html U www/future.html U gpsutils.c U devtools/ais.py U driver_italk.c U Makefile.am U gpsd.c U libgpsmm.cpp U test/stable/humminbird-M37.log.chk U test/stable/magellan-ec10.log.chk U test/stable/eXplorist210.log.chk U test/stable/italk-binary.log.chk U test/stable/magellan315.log.chk U test/stable/garmin48.log.chk U test/stable/uBlox-lea-4h.log.chk U driver_nmea.c _______________________________________________ Gpsd-dev mailing list Gpsd-dev@... https://lists.berlios.de/mailman/listinfo/gpsd-dev |
|
|
Re: VERSION->rev and SVN versionThe svn keywords:Id property is missing from something, I think. On Oct 6, 2009 12:07 PM, "Michael R. Davis" <mrdvt92@...> wrote: _______________________________________________ Gpsd-dev mailing list Gpsd-dev@... https://lists.berlios.de/mailman/listinfo/gpsd-dev |
|
|
Re: VERSION->rev and SVN versionNo, I'm wrong - brain very fuzzy today. I guess someone needs to hack
up the build script to autogenerate an "svn-version.h" or something that contains the current svn revision number of your repository. On Tue, Oct 6, 2009 at 12:12 PM, Chris Kuethe <chris.kuethe@...> wrote: > The svn keywords:Id property is missing from something, I think. > > On Oct 6, 2009 12:07 PM, "Michael R. Davis" <mrdvt92@...> wrote: > > I just updated to SVN 6393 but my deamon is still saying 6377. This needs > to track the the SVN or at least the lastest .c/.h file in SVN? > > $ svn update > At revision 6393. > > "rev":"$Id: gpsd_json.c 6377 2009-10-01 23:24:21Z esr $" > > $ svn update > U www/AIVDM.txt > U www/hacking.html > U www/future.html > U gpsutils.c > U devtools/ais.py > U driver_italk.c > U Makefile.am > U gpsd.c > U libgpsmm.cpp > U test/stable/humminbird-M37.log.chk > U test/stable/magellan-ec10.log.chk > U test/stable/eXplorist210.log.chk > U test/stable/italk-binary.log.chk > U test/stable/magellan315.log.chk > U test/stable/garmin48.log.chk > U test/stable/uBlox-lea-4h.log.chk > U driver_nmea.c > > > > > _______________________________________________ > Gpsd-dev mailing list > Gpsd-dev@... > https://lists.berlios.de/mailman/listinfo/gpsd-dev > -- GDB has a 'break' feature; why doesn't it have 'fix' too? _______________________________________________ Gpsd-dev mailing list Gpsd-dev@... https://lists.berlios.de/mailman/listinfo/gpsd-dev |
|
|
Re: VERSION->rev and SVN versionOn Tuesday 06 October 2009, Chris Kuethe wrote:
> No, I'm wrong - brain very fuzzy today. I guess someone needs to hack > up the build script to autogenerate an "svn-version.h" or something > that contains the current svn revision number of your repository. > > On Tue, Oct 6, 2009 at 12:12 PM, Chris Kuethe <chris.kuethe@...> wrote: > > The svn keywords:Id property is missing from something, I think. > > > > On Oct 6, 2009 12:07 PM, "Michael R. Davis" <mrdvt92@...> wrote: > > > > I just updated to SVN 6393 but my deamon is still saying 6377. This > > needs to track the the SVN or at least the lastest .c/.h file in SVN? > > > > $ svn update > > At revision 6393. > > > > "rev":"$Id: gpsd_json.c 6377 2009-10-01 23:24:21Z esr $" > > > > $ svn update > > U www/AIVDM.txt > > U www/hacking.html > > U www/future.html > > U gpsutils.c > > U devtools/ais.py > > U driver_italk.c > > U Makefile.am > > U gpsd.c > > U libgpsmm.cpp > > U test/stable/humminbird-M37.log.chk > > U test/stable/magellan-ec10.log.chk > > U test/stable/eXplorist210.log.chk > > U test/stable/italk-binary.log.chk > > U test/stable/magellan315.log.chk > > U test/stable/garmin48.log.chk > > U test/stable/uBlox-lea-4h.log.chk > > U driver_nmea.c > > > > > > > > > > _______________________________________________ > > Gpsd-dev mailing list > > Gpsd-dev@... > > https://lists.berlios.de/mailman/listinfo/gpsd-dev > echo REVISION=`svn info |grep ^Revision: | awk '{print $2}'` >revision That creates a file that can be sourced by scripts. Easy to change for a .h file. There is one problem with this. It relies on the builder (me) to make sure he is up to date and local edits are committed. Cheers, Remco -- Remco Treffkorn (RT445) HAM DC2XT remco@... (831) 685-1201 _______________________________________________ Gpsd-dev mailing list Gpsd-dev@... https://lists.berlios.de/mailman/listinfo/gpsd-dev |
|
|
Re: VERSION->rev and SVN versionOn Tue, Oct 6, 2009 at 3:44 PM, Remco Treffkorn <remco@...> wrote:
> echo REVISION=`svn info |grep ^Revision: | awk '{print $2}'` >revision which was roughly what i was thinking of > That creates a file that can be sourced by scripts. > Easy to change for a .h file. > > There is one problem with this. It relies on the builder (me) to make sure he > is up to date and local edits are committed. not really; svn status will tell you if you've got local changes. we can use that to generate an appropriate revision string - "SVN r6502 with local changes" for example -- GDB has a 'break' feature; why doesn't it have 'fix' too? _______________________________________________ Gpsd-dev mailing list Gpsd-dev@... https://lists.berlios.de/mailman/listinfo/gpsd-dev |
|
|
Re: VERSION->rev and SVN versionOn Tuesday 06 October 2009, Chris Kuethe wrote:
> On Tue, Oct 6, 2009 at 3:44 PM, Remco Treffkorn <remco@...> wrote: > > echo REVISION=`svn info |grep ^Revision: | awk '{print $2}'` >revision > > which was roughly what i was thinking of > > > That creates a file that can be sourced by scripts. > > Easy to change for a .h file. > > > > There is one problem with this. It relies on the builder (me) to make > > sure he is up to date and local edits are committed. > > not really; svn status will tell you if you've got local changes. we > can use that to generate an appropriate revision string - "SVN r6502 > with local changes" for example > This is like saying "we can send a man to the Moon". Certainly true, but not that easy. When I tried to figure out the solution to this problem, I ended up having to parse every line of output from 'svn status' and even apply some logic to the flags presented to come up with a final assessment of the state of affairs. I just seemed to be cheaper to put the burden on the 'build guy' (me). If you want to do it, I'd love to copy your solution... Cheers, Remco -- Remco Treffkorn (RT445) HAM DC2XT remco@... (831) 685-1201 _______________________________________________ Gpsd-dev mailing list Gpsd-dev@... https://lists.berlios.de/mailman/listinfo/gpsd-dev |
| Free embeddable forum powered by Nabble | Forum Help |