similar to: The case for freezing CRAN

On Fri, Mar 21, 2014 at 8:43 AM, Therneau, Terry M., Ph.D. < therneau@mayo.edu> wrote: [...] > > Gabor Csardi discussed the problems with maintaining a package with lots > of dependencies. > I maintain the survival package which currently has 246 reverse > dependencies and take a slightly different view, which could be described > as "the price of fame". I feel a

I’d like to nominate Quentin Colombet as LSR code owner. He has handled most of the reviews for me for the past couple years (thanks Quentin), and is willing to take on the responsiblity. Frankly, turning over ownership to Quentin is overdue. -Andy

Vagrant and packer look like the could be useful to developers, especially when testing, as they make it relatively painless to 'reinstall' a machine to a (mostly) known state. I find that, no matter how hard I try, there always seem to be a few keystrokes that don't make it into the changelog, and recreating from scratch is how I find them. Thanks for pointing them out. I would

There is a central assertion to this argument that I don't follow: > At the end of the day most published results obtained with R just won't be reproducible. This is a very strong assertion. What is the evidence for it? I write a lot of Sweave/knitr in house as a way of documenting complex analyses, and a glm() based logistic regression looks the same yesterday as it will

> On Nov 17, 2016, at 8:51 PM, Andrew Trick via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I’d like to nominate Quentin Colombet as LSR code owner. He has handled most of the reviews for me for the past couple years (thanks Quentin), and is willing to take on the responsiblity. Frankly, turning over ownership to Quentin is overdue. This also seems pretty obvious to me, and

I have tried 1.1.7. ./configure says: You need to install Xlib/Xfree... devel. I have installed x11proto-core-dev, which deprecates 'x-dev', 'cos x-dev is not applicable. Is it possible to edit configure so that it makes use of x11proto instead ? I assume asus 901 has Xandros on it, but some say it is Linpus. Xandros has not replied anything, asus support they have no responsiblity of

This is a brain-dump of my thoughts on the MCStreamer interface after several days of digging around trying to get a COFF writer working. All fragments should be associated with a symbol. For assembler components, a unnammed "virtual" symbol can be used when there is no explicit label defined. Section assignment should be the responsiblity of the object imlementing the MCStreamer

Hi, the master-compat branch in nouveau/linux-2.6 kernel tree has got a little bit out of hand. Distributions are packaging that, and I cannot know if they warn their users well enough about the hazards of using backported DRM (see: http://nouveau.freedesktop.org/wiki/UpstreamKernelIssues ). I originally intended master-compat as an easy way of installing the Nouveau flavour of DRM modules even

On May 4, 2010, at 11:03 AM, Nathan Jeffords wrote: > This is a brain-dump of my thoughts on the MCStreamer interface after several > days of digging around trying to get a COFF writer working. Great! Something that is worth pointing out is that the MCStreamer API is intended to directly reflect what is happening in .s files. We basically want one MCStreamer callback to correspond to one

> From: George Lin [mailto:glin@cosini.com] > > I want to deploy multiple SIPs phone in our office. And we have shutdown > the > firewall at our office router(with ip 211.x.x.x). we have deployed the > asterisk with IP 218.x.x.x. > > All SIP phones have 192.x.x.x. We have something similar George, * sits outside the firewall with a registered IP address, the SIP phones

This came up again recently with an irreproducible paper. Below an attempt to make a case for extending the r-devel/r-release cycle to CRAN packages. These suggestions are not in any way intended as criticism on anyone or the status quo. The proposal described in [1] is to freeze a snapshot of CRAN along with every release of R. In this design, updates for contributed packages treated the same as

I am assuming this an appropriate place to discuss this, but if it isn''t my apologies- just let me know. Just a Rails 4-ish thing. Am attempting to pull AMS (active_model_serializers), strong_parameters, and the "permitter" strategy that Adam Hawkins is using: http://broadcastingadam.com/2012/07/parameter_authorization_in_rails_apis/ Code so far is here (in the

On Wed, May 5, 2010 at 11:15 AM, Chris Lattner <clattner at apple.com> wrote: > On May 4, 2010, at 11:03 AM, Nathan Jeffords wrote: > ... We basically want one MCStreamer callback to correspond to one > statement in the .s file. This makes it easier to handle from the compiler > standpoint, but is also very important for the llvm-mc assembly parser > itself. > > This

On Thu, Sep 24, 2015 at 05:45:36PM +0200, Guus Sliepen wrote: > On Thu, Sep 24, 2015 at 05:51:30PM +0300, R?zvan Sandu wrote: > > > IMHO, we need: > > > > 1. A proper tinc.service file, included by default (prepackaged) in the > > stock .deb and .rpm packages in Fedora, Debian, Ubuntu, CentOS, etc. > > > > By "proper" I mean it will start

Dear All, I wonder whether anyone has an experience with FAME package written by Jeff Hallman. All my attempts to send him the following problem report did not succeed (the mail system says that my e-mail could not be delivered), so I turn for help to this list. I tried to use your FAME package written for R, but somehow I cannot get it working. I am using Windows XP and the newest R

>Personally, (Just my IMHO) CheckMail should go away. There are too >many different formats and it should not be SSHD's job to understand >them. It's biff and other evil program's responsiblity to do such >things. And IMHO PrintMOTD as well, since both CheckMail and PrintMOTD are often implemented either in a PAM module on some Linux systems or via the global shell

Would it not make more sense to have this on packagers responsiblity instead like you were saying adding it into the upstream repo. Maybe have a secondary repo that people can contribute to for distribution specific files and install scripts. On 24 September 2015 at 21:30, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Thu, Sep 24, 2015 at 05:45:36PM +0200, Guus Sliepen wrote: >

I'm writing a package that interfaces to the FAME database, via a library of compiled C routines accessible through a Linux .so file. My .onLoad() function loads the .so like this: dyn.load("/opt/fame/timeiq/lib/linux_x86/libjchli.so", local = F) and after that I also load my own fame.so via library.dynam("fame", package = "fame") The code in fame.so uses

My fame package has a function that checks to see if a FAME SERVER process is already running. On Linux, I can do this in one of two ways: pid <- Sys.getpid() user <- Sys.info()["user"] cmd <- paste("pgrep -fU", user, "-P", pid, "'FAME SERVER'") fameRunning <- as.logical(length(system(cmd, intern = T))) or I can use cmd

My fame package has to link to the libchli.so that comes with FAME. However, FAME is now supplying both 32 and 64 bit versions of the library. The 32-bit version is $FAME/hli/libchli.so while the 64-bit version is $FAME/hli/64/libchli.so. To set the right flags, it seems that I need to know, from within configure.ac, whether the R installation is 32 bit or 64 bit. Is there a way to detect this?