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. 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. Note, however, that this only supports

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

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

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

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

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

'Writing R Extensions', section 1.1.5, in the part about a package's 'inst' directory, says that if NEW is in both the top level and in the inst directory, the in inst will be installed: Note that with the exceptions of INDEX, LICENSE/LICENCE and NEWS, information files at the top level of the package will *not* be installed and so not be known to users of Windows and macOS

This bug appears in the current Windows build; I don't know if it applies generally. Duncan Murdoch On Fri, 26 Sep 2003 15:25:57 +1200 (NZST), Ray Brownrigg <ray@mcs.vuw.ac.nz> wrote: >If you INSTALL (Rcmd INSTALL) or cross-compile >(make PKGDIR=/pkg RLIB=/library pkg-mypkg) the copying of the inst >directory seems to happen very early in the process, *before anything is

This bug appears in the current Windows build; I don't know if it applies generally. Duncan Murdoch On Fri, 26 Sep 2003 15:25:57 +1200 (NZST), Ray Brownrigg <ray@mcs.vuw.ac.nz> wrote: >If you INSTALL (Rcmd INSTALL) or cross-compile >(make PKGDIR=/pkg RLIB=/library pkg-mypkg) the copying of the inst >directory seems to happen very early in the process, *before anything is

Hi Ovirt node image build problem? Node image build my system OS Fedora core 14. I am have a question about installation process of oVirt project. Install DOC : https://fedorahosted.org/ovirt/wiki/Build But node-image build error? [root at Ovirt-T node]# make publish { test ! -d "ovirt-node-1.9.3" || { find "ovirt-node-1.9.3" -type d ! -perm -200 -exec chmod u+w

On Mon, Oct 05, 2015 at 05:05:32PM +0100, Richard W.M. Jones wrote: > On Mon, Oct 05, 2015 at 06:12:03PM +0300, Roman Kagan wrote: > > On Mon, Oct 05, 2015 at 02:17:52PM +0100, Richard W.M. Jones wrote: > > > This doesn't appear in EXTRA_DIST, so it won't be copied to the tarball. > > > > Didn't know that. How is the tarball generated, so that I can test

Hi Ovirt node image build problem? Node image build my system OS Fedora core 14. I am have a question about installation process of oVirt project. Install DOC : https://fedorahosted.org/ovirt/wiki/Build But node-image build error? [root at Ovirt-T node]# ./autogen.sh I am going to run ./configure with no arguments - if you wish to pass any to it, please specify them on the

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

Hi Tanya, The first thing you need to understand is that there are multiple make targets to support this feature. I'll briefly describe each here so you have an overview and then delve into the details later. * distdir - builds the distribution directory from which the distribution will be packaged * dist - builds each of the distribution tarballs (tar.gz,

For reasons unrelated to NUT, I upgraded my FreeBSD-x86 buildslave machine from 9.1 to 10.0. This involved rebuilding the whole ports tree, but no other (intentional) changes were made. Now, I get this error: (cd scripts && make top_distdir=../nut-2.7.1.5 distdir=../nut-2.7.1.5/scripts \ am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir) make[4]: don't

For reasons unrelated to NUT, I upgraded my FreeBSD-x86 buildslave machine from 9.1 to 10.0. This involved rebuilding the whole ports tree, but no other (intentional) changes were made. Now, I get this error: (cd scripts && make top_distdir=../nut-2.7.1.5 distdir=../nut-2.7.1.5/scripts \ am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir) make[4]: don't