[Qgis-developer] INSTALL doc and svn/git

2011-05-08 Thread William Kyngesburye
While looking over the Mac build instructions for 1.7 release, I realized the 
whole SVN section will have to be changed to be about git.

Then it occurred to me - why are we mentioning getting source from svn (now 
git) at all for a release?  This is in a released source package.  Of course, 
svn/git applies to trunk (now master).

Maybe to accomodate both a release and git the body platform sections could be 
about release packages, with reference to a separate section at the end (after 
all platform sections) that covers git for those interested.  That would also 
reduce some redundancy in describing git setup and commands.

-
William Kyngesburye kyngchaos*at*kyngchaos*dot*com
http://www.kyngchaos.com/

Time is an illusion - lunchtime doubly so.

- Ford Prefect


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [Qgis-developer] INSTALL doc and svn/git

2011-05-08 Thread William Kyngesburye
This is what I had in mind, but I didn't think about the CODING file, I guess 
the git stuff can be moved there, though that might be info overload for casual 
users that want to try development sources:

http://github.com/kyngchaos/Quantum-GIS/commit/1ecfd9b0addec28494f0331b3446bcf60273f053

Only the Mac section is updated here to refer to the git section and to have 
git installation instructions.  Similar would be needed for Linux and Windows.

On May 8, 2011, at 2:46 PM, Tim Sutton wrote:

 Hi William
 
 On Sun, May 8, 2011 at 6:55 PM, William Kyngesburye
 wokl...@kyngchaos.com wrote:
 While looking over the Mac build instructions for 1.7 release, I realized 
 the whole SVN section will have to be changed to be about git.
 
 Then it occurred to me - why are we mentioning getting source from svn (now 
 git) at all for a release?  This is in a released source package.  Of 
 course, svn/git applies to trunk (now master).
 
 Maybe to accomodate both a release and git the body platform sections could 
 be about release packages, with reference to a separate section at the end 
 (after all platform sections) that covers git for those interested.  That 
 would also reduce some redundancy in describing git setup and commands.
 
 
 Yeah or we should just move all git related stuff into CODING.t2t
 which is intended for developers (who are probably more likely to
 actually care about such things)and just put a note referring to
 that file in the INSTALL.t2t docs.
 
 Regards
 
 Tim
 
 
 -
 William Kyngesburye kyngchaos*at*kyngchaos*dot*com
 http://www.kyngchaos.com/
 
 Time is an illusion - lunchtime doubly so.
 
 - Ford Prefect
 
 
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer
 
 
 
 
 -- 
 Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
 ==
 Please do not email me off-list with technical
 support questions. Using the lists will gain
 more exposure for your issues and the knowledge
 surrounding your issue will be shared with all.
 
 Visit http://linfiniti.com to find out about:
  * QGIS programming and support services
  * Mapserver and PostGIS based hosting plans
  * FOSS Consulting Services
 Skype: timlinux
 Irc: timlinux on #qgis at freenode.net
 ==
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

-
William Kyngesburye kyngchaos*at*kyngchaos*dot*com
http://www.kyngchaos.com/

All generalizations are dangerous, even this one.


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer