similar to: [PATCH v2] Makefile: add support for git svn clones

git has an interface for cloning SVN repositories into git which some users might decide to use. For those users' surprise, the repository will always fail to build on svnonly target and it will exit early. The problem is simple enough to fix by just checking if a .git directory exists in top_builddir and, if so, call git svn info insstead of svn info. Signed-off-by: Felipe Balbi <balbi

On 19/01/2015 2:33 PM, Felipe Balbi wrote: > git has an interface for cloning SVN repositories into git which > some users might decide to use. For those users' surprise, the > repository will always fail to build on svnonly target and it will > exit early. > > The problem is simple enough to fix by just checking if a .git > directory exists in top_builddir and, if so,

git has an interface for cloning SVN repositories into git which some users might decide to use. For those users' surprise, the repository will always fail to build on svnonly target and it will exit early. The problem is simple enough to fix by just checking if a .git directory exists in top_builddir and, if so, call git svn info insstead of svn info. Signed-off-by: Felipe Balbi <balbi

Hi, On Mon, Jan 19, 2015 at 03:06:11PM -0500, Duncan Murdoch wrote: > On 19/01/2015 2:33 PM, Felipe Balbi wrote: > > git has an interface for cloning SVN repositories into git which > > some users might decide to use. For those users' surprise, the > > repository will always fail to build on svnonly target and it will > > exit early. > > > > The problem

Hi, On Mon, Jan 19, 2015 at 03:31:32PM -0500, Duncan Murdoch wrote: > >>> git has an interface for cloning SVN repositories into git > >>> which some users might decide to use. For those users' > >>> surprise, the repository will always fail to build on svnonly > >>> target and it will exit early. > >>> > >>> The

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 19/01/2015 3:20 PM, Felipe Balbi wrote: > Hi, > > On Mon, Jan 19, 2015 at 03:06:11PM -0500, Duncan Murdoch wrote: >> On 19/01/2015 2:33 PM, Felipe Balbi wrote: >>> git has an interface for cloning SVN repositories into git >>> which some users might decide to use. For those users' >>> surprise, the

Hi, On Mon, Jan 19, 2015 at 03:44:45PM -0500, Duncan Murdoch wrote: > >>>>> git has an interface for cloning SVN repositories into git > >>>>> which some users might decide to use. For those users' > >>>>> surprise, the repository will always fail to build on > >>>>> svnonly target and it will exit early. >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 19/01/2015 3:34 PM, Felipe Balbi wrote: > Hi, > > On Mon, Jan 19, 2015 at 03:31:32PM -0500, Duncan Murdoch wrote: >>>>> git has an interface for cloning SVN repositories into git >>>>> which some users might decide to use. For those users' >>>>> surprise, the repository will always fail

On 19/01/2015 4:13 PM, Nathan Kurz wrote: > On Mon, Jan 19, 2015 at 1:00 PM, Felipe Balbi <balbi at kernel.org> wrote: >> I just thought that such a small patch which causes no visible change to >> SVN users and allow for git users to build R would be acceptable, but if >> it isn't, that's fine too. > > Felipe --- > > It would appear that you are

Fellipe, CXXR development has moved to github, and we haven't fixed up the build for using git yet. Could you send a pull request with your change to the repo at https://github.com/cxxr-devel/cxxr/? Also, this patch may be useful for pqR too. https://github.com/radfordneal/pqR Thanks On Mon, Jan 19, 2015 at 2:35 PM, Dirk Eddelbuettel <edd at debian.org> wrote: > > On 19

this is from a fresh svn checkout: [stvjc at stvjc1 R-devel]$ ls -tl Makefile -rw-rw-r-- 1 stvjc stvjc 12833 Jun 26 07:24 Makefile [stvjc at stvjc1 R-devel]$ svn up At revision 45988. [stvjc at stvjc1 R-devel]$ bin/R R version 2.8.0 Under development (unstable) (--) Copyright (C) The R Foundation for Statistical Computing ISBN 3-900051-07-0 .. > sessionInfo() R version 2.8.0 Under

Dear R-devel, I checked out a recent copy of R via Subversion and made a few changes to the code. I wanted to commit them locally to my repo, just to stay organized and keep them separate from other changes I plan to make. However, I was not able to commit them because I don't think SVN allows this? Plan B, check out a Git mirror of R, https://github.com/wch/r-source/ It has some

>>>>> G?bor Cs?rdi >>>>> on Thu, 26 Dec 2019 08:23:10 +0000 writes: > Hi Frederick, I know some non R-core people use this > workflow to keep local patches in git branches: > https://bookdown.org/lionel/contributing/ > Best, Gabor Thank you, Gabor, and notably, Lionel, for providing the extras. As Frederik notes / ask as well about

On Mon, Jan 19, 2015 at 1:00 PM, Felipe Balbi <balbi at kernel.org> wrote: > I just thought that such a small patch which causes no visible change to > SVN users and allow for git users to build R would be acceptable, but if > it isn't, that's fine too. Felipe --- It would appear that you are unaware that you are walking a minefield of entrenched positions and personality

Hello all, I'm trying to build R 32bit from source in a Windows 64 machine. I have followed the steps in "R Installation and Adiministration" ( http://cran.r-project.org/doc/manuals/R-admin.html#Getting-the-source-files) or at least I think I did everything described. I am not sure if I have installed the libjpeg, libtiff and libpng files though. I have upzipped them in the

On 19 January 2015 at 17:11, Duncan Murdoch wrote: | The people who would have to maintain the patch can't test it. I don't understand this. The patch, as we may want to recall, was all of +GIT := $(shell if [ -d "$(top_builddir)/.git" ]; then \ + echo "git"; fi) + and - (cd $(srcdir); LC_ALL=C TZ=GMT svn info || $(ECHO) "Revision: -99")

Dear R People: I'm installing R 2-.15.1 on a Windows 32 bit machine from source. I'm getting a strange error about init.win (please see below) Does this look familiar to anyone, please? Thanks, Erin Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. c:\R\R-2.15.1\src\gnuwin32>make all recommended make all recommended make[1]:

I'm trying to build from the latest SVN sources on Mac OS X 10.4.3 and I seem to be having a problem making the documentation. When I do make install, i get the following: (sly at gigondas):~/src/R/r-devel/build-f95$ make install make[1]: Nothing to be done for `front-matter'. SVN-REVISION is unchanged make[1]: Nothing to be done for `install'. make[1]: Nothing to be done for

Dear R People: I'm trying to compile R-2.15.0 on a 64 bit Windows machine. However, I'm getting the following error: c:\R64\R-2.15.0\src\gnuwin32>set TMPDIR=c:\temp set TMPDIR=c:\temp c:\R64\R-2.15.0\src\gnuwin32>make all recommended make all recommended make[1]: `MkRules' is up to date. make[4]: Nothing to be done for `svnonly'. installing C headers make[2]: Nothing to

>>>>> <frederik at ofb.net> >>>>> on Tue, 24 May 2016 15:15:17 -0700 writes: > Thank you, Martin. I linked to your message in a comment here so maybe > other people will know about that useful technique: > http://singmann.org/installing-r-devel-on-linux/#comment-161 > However, when I try it, I get an error: > $ make