[GRASS-dev] SVN trunk issue with g.list and g.remove (and solution)

Huidae Cho grass4u at gmail.com
Thu Oct 2 07:17:17 PDT 2014


On Wed, Oct 01, 2014 at 10:43:54PM +0200, Markus Metz wrote:
> On Tue, Sep 30, 2014 at 8:16 PM, Huidae Cho <grass4u at gmail.com> wrote:
> > Hmm... I "remove"d g.list/g.remove and "rename"d g.mlist/g.mremove. Maybe,
> > there is a better way?
> 
> Did you "remove" or "svn remove"? Same for "rename". I guess you did
> "svn [remove|rename]", and some other people did not "make distclean"
> before "svn up". FWIW, I had no problems with your changes, doing
> "make distclean" before "svn up".

Yes, I did "svn remove" and "svn rename". Of course, I had to "make
distclean". IMHO, "svn up" before "make distclean" shouldn't affect
compilation because "make distclean" has nothing to do with the svn
repository, but "make distclean" is necessary after or before "svn up"
anyway.

Regards,
Huidae

> 
> Whoever compiles GRASS from source and wants the latest and greatest
> (svn up), must clean the source code first with "make distclean"
> before recompiling. This applies to all 4 branches. This is not GRASS
> specific but the way how svn works.
> 
> Markus M
> 
> >
> > On Tue, Sep 30, 2014 at 1:19 PM, Vaclav Petras <wenzeslaus at gmail.com> wrote:
> >>
> >>
> >>
> >> On Tue, Sep 30, 2014 at 12:02 PM, Markus Neteler <neteler at osgeo.org>
> >> wrote:
> >>>
> >>> On Tue, Sep 30, 2014 at 5:25 PM, Vaclav Petras <wenzeslaus at gmail.com>
> >>> wrote:
> >>> ...
> >>> > Confirmed, I had to do the same in all copies too some time ago. SVN is
> >>> > not
> >>> > really good at renaming and deleting things, it is always confused and
> >>> > I
> >>> > really don't understand why I need to do revert.
> >>>
> >>> As this almost never happened, it may have been this specific commit
> >>> being different from others.
> >>> Whatever, the solution we have.
> >>>
> >> Oh, now I hope it was not because I recommended some Git-like procedure to
> >> Huidae which is not really what SVN wanted. Anyway, it was easy to solve
> >> although it required manual intervention to automatic builds (at least the
> >> one for tests).
> >>
> >>
> >>>
> >>> Markus
> >>
> >>
> >>
> >> _______________________________________________
> >> grass-dev mailing list
> >> grass-dev at lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/grass-dev
> >
> >
> >
> > _______________________________________________
> > grass-dev mailing list
> > grass-dev at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/grass-dev


More information about the grass-dev mailing list