As you already pointed out, it is rather simple to use git-describe to generate assemblyinfos. Ayende also used some compiler directive to suppress the warning when adding the SHA1 to the Output in Rhino.Mocks, a road I didn't want to go down.
As for the tags, if we use git-describe it should be pretty easy to create a tag for the latest released version on the appropriate repositories. Pathing and Git: I haven't exactly had the best of luck with exporting patches and then applying them. I tried a few times while learning how to do handle git correctly and usually I couldn't apply the patch later. But I know this works, I just didn't figure it out right away. If anyone has seen a good article on that please shoot me an email. As for pull requests: I think this will revolutionize the way we handle patches. greetings Daniel On Sat, Jan 30, 2010 at 9:53 PM, Mauricio Scheffer < [email protected]> wrote: > Only problem with this is that not all projects have tags yet, so git > describe would fail there. Some sort of fallback has to be devised for > these cases. > > BTW it would be great if you could fork > http://github.com/castleproject/Castle.Buildscripts > and implement this :-) > > On Jan 29, 1:46 pm, Andre Loker <[email protected]> wrote: > > On 29 Jan., 16:59, Mauricio Scheffer <[email protected]> > > wrote: > > > > > +1. This currently throws a warning "Assembly generation -- The > > > version '1.0.1.27/1dd3-master build 6' specified for the 'product > > > version' is not in the normal 'major.minor.build.revision' format" but > > > it seems that the warning is removed in .net 4.0:http://bit.ly/aWIYeX > > > > You can safely ignore/disable the warning: > > > > "You can ignore this warning if you encounter it when you create a > > AssemblyInformationalVersionAttribute. The informational version is a > > string that attaches additional version information to an assembly; > > this information is not used at run time. Although you can specify any > > text, a warning message appears on compilation if the string is not in > > the format that is used by the assembly version number, or if it is in > > that format but contains wildcard characters. This warning is > > harmless." > > > > http://msdn.microsoft.com/en-us/library/4a0640cd.aspx > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" group. > To post to this group, send email to [email protected] > . > To unsubscribe from this group, send email to > [email protected]<castle-project-devel%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/castle-project-devel?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
