>>>>>>>>> Is there a way to move ekiga.rc from root to win32? >>>>>>>> >>>>>>>> 1) git mv ekiga.rc win32/ >>>>>>>> 2) make sure any file referencing ekiga.rc now searches for it in >>>>>>>> win32/ >>>>>>>> >>>>>>>> Snark >>>>>>> >>>>>>> Could you please rename it so that the basename is distinctive, e.g. >>>>>>> ekiga-rc.rc ? I ask this because eventually we can include >>>>>>> compilation >>>>>>> of the resources into the autoconf/libtool make process and then an >>>>>>> ekiga.o file would be a bit dangerous I think. Additionally VALUE >>>>>>> "SpecialBuild", CVS_VERSION in the resource file is a bit outdated. >>>>>>> Now >>>>>>> an EKIGA_REVISION is defined in src/revision.h . See attached patch >>>>>>> as >>>>>>> an example for how one could handle the Win32 resources. >>>>>> >>>>>> Note that ekiga uses git now, so src/Makefile.am info about revision.h >>>>>> is >>>>>> obsolete... Is it interesting to resuscitate it? >>>>>> >>>>>> -- >>>>>> Eugen >>>>> >>>>> Yes, I have seen that. I am still testing. Would something like >>>>> #define EKIGA_REVISION "EKIGA_3_2_0-80-g80bf6d3" be acceptable in >>>>> revisioin.h? It is based on the output of git describe, the 80th >>>>> revision of tag EKIGA_3_2_0 I guess. > > It's ok for me. > > How did you obtain 80 and g80bf...? I couldn't find them on > http://git.gnome.org/cgit/ekiga/, neither with git log on both trunk and > gnome-2-26. I didn't know it is possible to number the revisions (80) in > git.
At a guess the g80.... is the short version of the git revision (it uses the first 8 digits or something) and at a guess the 80 is the local debian build number (because the git revs don't necessarily increment in the way the average package management system would think that a later than the previous version). Peter _______________________________________________ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
