similar to: [PATCH] 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. Note, however, that this only supports

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,

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

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: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

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: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

-----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 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

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

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

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

Hello, I was trying to build R from source on Windows XP. I installed software which are mentioned from the follow web page http://www.murdoch-sutherland.com/Rtools/ (Last accessed on Nov. 13th, 2006) . Unfortunately, I got error messages whenever I run 'make all recommended' without modifying 'MkRules' file. I have removed software and reinstalled them several times but I still

Hello! I'm trying to install R-patched from source on a Windows 64 bit laptop. I have installed R-tools 2.16 and set up the jpeg, tiff, and libpng files Here is the output: c:\R64\R-patched\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 be done for

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

Hi Damien! I produced a little patch to the package ver. 4.6p1 for linux. My company, for many bureaucratic reasons, was interested in triggering each uploaded file to the server using sftp subsystem. In Internet and in ML, all folks solve the problem using a script joining sftp command section to ssh command section, but unfortunately isn't my case. The patch consist in a

Dear R People: I'm starting to think that I should just install from the binary, but here is my latest effort to install from source on a Windows 7 64 bit: c:\R64\R-patched>cd src cd src c:\R64\R-patched\src>cd gnuwin32/ cd gnuwin32/ c:\R64\R-patched\src\gnuwin32>set TMPDIR=c:\temp set TMPDIR=c:\temp c:\R64\R-patched\src\gnuwin32>make all recommended make all recommended