similar to: [LLVMdev] A better CMake

tags 407143 +patch thanks On Fri, 2013-08-16 at 14:42 +0100, Ian Campbell wrote: > tags 688308 +patch > thanks > > A lot of /docs/ is pretty low-level and not all that interesting to be > installed by the packages. However some of it is, and in particular some > is referenced from the manpages. I've cherry-picked the bits which I > think are most interesting in that

tags 688308 +patch thanks A lot of /docs/ is pretty low-level and not all that interesting to be installed by the packages. However some of it is, and in particular some is referenced from the manpages. I've cherry-picked the bits which I think are most interesting in that context. Patch below. 8<--------------- commit 7f8ac283e684b7c713d52ed845cab0704a97abab Author: Ian Campbell <ijc

I have a function: source_dir <- function(path, pattern = "\\.[rR]$", chdir = TRUE) ... documented with ... \usage{source_dir(path, pattern="\\.[rR]$", chdir=TRUE)} ... But I get Codoc mismatches from documentation object 'source_dir': source_dir Code: function(path, pattern = "\\.[rR]$", chdir = TRUE) Docs: function(path, pattern =

On UNIX, I am executing an rsync command, from within a script. The command goes something like this: /usr/bin/rsync --verbose --progress --stats --compress --recursive --times --perms --links --safe-links source_dir/ user at target_machine:/parent_path/source_dir In other words, I am replicating source_dir on a remote machine. It ends up next to a lot of sibling, directories, like this: On

I'm using a little shell script: BUILD_ROOT=/home/llvm-1.7/cfrontend PREFIX="$BUILD_ROOT/install" LOCAL_BUILD_DIR="$BUILD_ROOT/build" SOURCE_DIR="$BUILD_ROOT/src" echo $__me: Building $TARGET echo $__me: BUILD_ROOT == $BUILD_ROOT echo $__me: SOURCE_DIR == $SOURCE_DIR echo $__me: LOCAL_BUILD_DIR == $LOCAL_BUILD_DIR echo $__me: PREFIX == $PREFIX

Hi, I am trying to install pdftools package on R 3.3.1 (Ubuntu 16.04), but the following issue occurs: ------------------------- ANTICONF ERROR --------------------------- Configuration failed because poppler-cpp was not found. Try installing: * deb: libpoppler-cpp-dev (Debian, Ubuntu, etc) * rpm: poppler-cpp-devel (Fedora, CentOS, RHEL) * csw: poppler_dev (Solaris) * brew: poppler (Mac OSX)

Hi there, I am using rsync to synchronize two folders. I have configured the log-format to my personal needs like this: --log-format="%f %t %o %l %P" I am also using the --delete flag to log deleted files as well. I have upgraded my rsync version to 2.6.9 when I figured out that starting with version 2.6.4 the log format had been enhanced to also include the "del."

Hello, libpoppler-cpp-dev is not an R package but a system library to be installed with (for example) : sudo apt-get install libpoppler-cpp-dev hope this help. Fran?ois Guilhaumon ?? Fran?ois Guilhaumon, research scientist (IRD <http://en.ird.fr>), associate editor (Journal of Biogeography <http://onlinelibrary.wiley.com/journal/10.1111/%28ISSN%291365-2699>). homepage :

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1328707901 -3600 # Node ID b730f1f980bdc1edcebf7dbbbb5253ccafcd8c04 # Parent 3574f4d67843733ccaabab5f8ebb859c99d7314a remove references to removed libflask from setup.py Build in SLES11 SP1/2 fails after libflask removal. > building ''flask'' extension > error: ../../tools/flask/libflask/libflask.so: No

Hi Francois, Thanks for your quick response. Actually, I had already done that... sudo apt-get install libpoppler-cpp-dev Reading package lists... Done Building dependency tree Reading state information... Done libpoppler-cpp-dev is already the newest version (0.41.0-0ubuntu1.1). 0 upgraded, 0 newly installed, 0 to remove and 107 not upgraded. Therefore, I assume I have this installed. Best

i am trying to install xml2 from CRAN, and it is throwing an error that it cannot find the libxml2 library configuration. The thing is that pkg-config seems to be set up correctly: $ echo $PKG_CONFIG_PATH :/usr/local/opt/libxml2/lib/pkgconfig:/usr/local/opt/libxml2/lib/pkgconfig $ pkg-config --cflags --libs libxml-2.0 -I/usr/local/Cellar/libxml2/2.9.7/include/libxml2

Hi all, I'm running the following rsync job via cron: rsync --recursive --compress --human-readable --progress --update --perms --chmod=a-w -e "ssh -i /rsync-key" user@host:/source_dir/ /target_dir rsync: failed to set permissions on "/target_dir/.": Operation not permitted (1) rsync: failed to modify permissions on "/target_dir/.": Operation not permitted (1)

rsync Folks, The following explanatory text is by me and the patches are by Rowan McKenzie for use by the Advanced Scientific Computing group at CSIRO. This patch builds upon the --link-dest patch by Bryant Hansen (Thanks heaps!). 1. The original patch provided an alternate behaviour for rsync when using the --link-dest option. When there are identical files in the source and link-dest areas,

Greg Pettyjohn <gregp at ccs.neu.edu> writes: > I'm using a little shell script: [snip] > confopts="--prefix=$PREFIX" > confopts="$confopts --disable-threads" > confopts="$confopts --disable-nls" > confopts="$confopts --disable-shared" > confopts="$confopts --enable-languages=c,c++" >

Changes since last time: - split auto-generated code in to c and h files - un-break the build system - fix ocaml binding due to libxl API change - lot''s of tidy-ups too numerous to mention Please consider and apply :) -----8<--------------------------------------------------------------- Introduce python binding for libxl. The binding is not yet complete but list_domains,

puppetlabs_spec_helper is a Rubygem to make writing and running module spec tests using rspec-puppet easier. It includes a set of common rake tasks and a spec_helper that correctly initializes puppet and rspec-puppet for testing. The code is available on github at http://github.com/puppetlabs/puppetlabs_spec_helper. Patches are welcome. To convert a module with existing spec tests to use the

Hi all, I'm running rsync version 2.6.3 protocol version 28 on Solaris 8 and am having a problem. We have some scripts that wrap around rsync and generate a list of files to transfer from the sending system (regardless of whether that directory exists on the receiver). I was expecting rsync to fail when transferring files with a path that doesn't exist on the receiver (in fact

Thanks. I'll try some of this. Further comments in-line: On Sun, 23 Apr 2006, Oscar Fuentes wrote: > Greg Pettyjohn <gregp at ccs.neu.edu> writes: > > > I'm using a little shell script: > [snip] > > confopts="--prefix=$PREFIX" > > confopts="$confopts --disable-threads" > > confopts="$confopts --disable-nls" >

This is odd: We're using rsync to mirror multiple directories from a server to two clients. The server is running Tru64 v5.1a, client A is running Redhat Linux 8.0, and client B is running Tru64 v4.0g. The mirrors for both clients are running at the same time interval (10 minutes, offset by 5 minutes). All machines are running rsync v2.5.6, and using ssh2 v3.2.3 as the

https://bugzilla.samba.org/show_bug.cgi?id=11027 Bug ID: 11027 Summary: Sticky bit not set when using --chmod=D+t alone, without --perms Product: rsync Version: 3.0.9 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: