On Tue, May 26, 2015 at 10:46 AM, Gabriel Becker wrote:
> That's true, but issues, checkouts, comments, credit, etc should all be
> going to the original repo. Anything else seems grossly unfair to the
> package author(s). This issue is exacerbated even further when the the
> author isn't developi
What you are doing is great, and that's a pretty clear warning (I would go
ahead and add "DO NOT FORK ME" to the verbiage since I am one of the
dumbasses who submitted a pull request in such a fashion, whereupon the
original author got to set up a Git repo, I re-PR'ed against that, and all
was well
Or maybe it would be sensible to ask GitHub if they can fix this.
If it's a common-ish use case (e.g. for mirrors), it's not something that
should be terribly challenging engineering-wise, and it would prevent a lot
of hooha.
Funfact: GitHub is run and staffed by actual people, most of them prett
On Tue, May 26, 2015 at 2:10 PM, Gabriel Becker
wrote:
[...]
>
> Well, sort of. I mean if the package is being actively developed not on
> github, forking your archive repo and developing a patch/etc against it
> won't necessarily be particularly effective, as there is no way to have the
> right
On Tue, May 26, 2015 at 10:55 AM, Gábor Csárdi
wrote:
> On Tue, May 26, 2015 at 1:46 PM, Gabriel Becker
> wrote:
>
>> That's true, but issues, checkouts, comments, credit, etc should all be
>> going to the original repo.
>
>
> You mean the links? They are, aren't they?
>
Sort of, the link for b
On Tue, May 26, 2015 at 2:01 PM, Dan Tenenbaum
wrote:
[...]
>
> No, but you can set up a 'bot' which listens for pull requests and then
> immediately denies them with a customizable message, perhaps giving people
> the url where they should be making their pull requests. Example:
> https://gith
- Original Message -
> From: "Gábor Csárdi"
> To: "Gabriel Becker"
> Cc: "Simon Urbanek" , "Rainer M Krug"
> , r-devel@r-project.org
> Sent: Tuesday, May 26, 2015 10:55:02 AM
> Subject: Re: [Rd] MetaCran website v1.0.0-alpha
>
> On Tue, May 26, 2015 at 1:46 PM, Gabriel Becker
>
> wro
On Tue, May 26, 2015 at 12:45 AM, Gábor Csárdi wrote:
> On Mon, May 25, 2015 at 8:28 PM, Simon Urbanek
> wrote:
>
>> One issue I have with this is that it doesn't point to the original GitHub
>> repositories of the packages, so you end up with additional repositories on
>> Github in Gabor's name
On Tue, May 26, 2015 at 1:46 PM, Gabriel Becker
wrote:
> That's true, but issues, checkouts, comments, credit, etc should all be
> going to the original repo.
You mean the links? They are, aren't they?
[...]
> >From the email Gabor just sent out, it sounds like he and I agree about
> this stu
On Tue, May 26, 2015 at 1:43 PM, Henrik Bengtsson wrote:
[...]
> If people send pull requests, maybe adding a generic open pull request
> to each repository with title "MIRROR ONLY: Do not send pull requests
> here" would help. The fancy version would be to say "MIRROR ONLY: All
> patches/pull r
That's true, but issues, checkouts, comments, credit, etc should all be
going to the original repo. Anything else seems grossly unfair to the
package author(s). This issue is exacerbated even further when the the
author isn't developing the package on github at all, and github users may
unintention
On Tue, May 26, 2015 at 1:26 PM, Hadley Wickham wrote:
> > Maybe I'm missing something, but why would you fork the repo instead of
> > just using the existing repo?
>
> One advantage of a fork is that you have permanent archive even if the
> original goes away.
>
Exactly. Even if the original re
On Tue, May 26, 2015 at 12:18 PM, Gabriel Becker wrote:
> On Tue, May 26, 2015 at 9:25 AM, Yihui Xie wrote:
>
>> I cannot speak for other package authors, but for all my own packages,
>> I have provided the BugReports field in DESCRIPTION that points to the
>> Github issues page. You can probably
On Tue, May 26, 2015 at 9:25 AM, Yihui Xie wrote:
> I cannot speak for other package authors, but for all my own packages,
> I have provided the BugReports field in DESCRIPTION that points to the
> Github issues page. You can probably use this field to check if a
> package is on Github or not. If
I cannot speak for other package authors, but for all my own packages,
I have provided the BugReports field in DESCRIPTION that points to the
Github issues page. You can probably use this field to check if a
package is on Github or not. If it is, you may just fork the original
repo instead of creat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
False alarm. Completely wiping out my build directory followed by
../R-devel/configure --with-tcl-config=/usr/lib/tclConfig.sh
- --with-tk-config=/usr/lib/tkConfig.sh; make
seems to work. (My fault for assuming repeated cycles of
./configure;
Ben,
At work with little time so _real brief_:
-- we build r-devel "all the time", in fact nightly for rocker; and there
are Dockerfiles to look at
-- we build R all the time in Debian, Ubuntu, ... and my sources for that
are not on GH but you can fetch the diff.gz
-- there is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm having some issues trying to compile R-devel on Ubuntu 14.04.
library("tcltk") works fine on the version of R as installed from
Debian packages; I've done "apt-get build-dep r-base" so I think I
have all the tcltk libraries I need installed ...
Hi all,
There is a compatibility issue between the package 'lme4' and my package
'kml'. I define the "[" operator. It works just fine in my package (1). If I
try to use the lme4 package, then it does no longer work (2). Moreover, it
has some kind of strange behavior (3). Do you know what is wrong?
On Mon, May 25, 2015 at 8:28 PM, Simon Urbanek
wrote:
> One issue I have with this is that it doesn't point to the original GitHub
> repositories of the packages, so you end up with additional repositories on
> Github in Gabor's name that have nothing to do with the actual Github
> repositories o
Am .05.2015, 09:01 Uhr, schrieb Richard Cotton :
On 25 May 2015 at 19:43, Duncan Murdoch wrote:
http://stackoverflow.com/questions/17715956/why-do-some-unicode-characters-display-in-matrices-but-not-data-frames-in-r
Yes, but it is a bug, just a hard one to fix. It needs someone to
dedicat
On 25 May 2015 at 19:43, Duncan Murdoch wrote:
>> http://stackoverflow.com/questions/17715956/why-do-some-unicode-characters-display-in-matrices-but-not-data-frames-in-r
> Yes, but it is a bug, just a hard one to fix. It needs someone to dedicate
> a serious amount of time to deal with it.
>
> S
22 matches
Mail list logo
