On Thu, Jan 12, 2012 at 2:24 AM, Alvaro Lopez Ortega <[email protected]>wrote:
> Since this is not an actual release, I did not tagged the repo (Maybe I > should have). I would definitely tag anything that's been pushed out into the public ether for evaluation. If for no other reason (and there are several*) it allows for ease of using git to push out experimental changes, applied patches, etc. in which we can then switch back and forth between branches/tags without need to download and extract a new tarball. * Since `make` will keep track of changed files and only rebuild the .o file related to those files it avoids having to reconfigure/rebuild everything even if only minor changes have been made. Obviously not a good practice when switching between major releases where make may not pick up on all changes made to the overall build process, for smaller changes this is much preferable IMO. * Given github will generate a tarball for each new tag, for those not using git it makes it easier to manage the downloads related to each tagged entry.** ** The one caveat to this is that the source of external modules will not be included in the tarball so an additional step would need to be added to the makefile to check whether or not the source for a given submodule exists and if doesn't download and extracted the related tagged tarball from the related project before preceding with the build. -- /M:D M. David Peterson Co-Founder & Chief Architect, 3rd&Urban, LLC Email: [email protected] Voice: (801) 742-1064 http://amp.fm | http://mdavidpeterson.com
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
