To add my two-pence regarding duplication.
I think this is a judgement call.
If the functionality would be precisely the same and for the same situations then there are some instances where you would still want to duplicate but generally probably not. An example would be where the function is small and easy to code but depending on the existing package would bring a large reverse dependency that you don't want to have.
Thanks,
Rebecca
----------------------------------------------------------------------
Message: 1
Date: Sat, 8 Sep 2018 21:11:46 -0400
From: Joseph Wood <jwood000 at gmail.com>
To: r-package-devel at r-project.org
Subject: [R-pkg-devel] Package Etiquette
Message-ID:
<CAKDcrSjmmt_VsZk=KjiyfPCnbTfmOTOzwLfcsepTpRPnWRPj+g at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi all,
I?m a new developer and this is my first post. I have a question regarding
package development with regards to duplication of functionality. I read
the posting guide (https://www.r-project.org/posting-guide.html) and didn?t
R: Posting Guide: How to ask good questions that prompt ...<https://www.r-project.org/posting-guide.html>
www.r-project.org
Posting Guide: How to ask good questions that prompt useful answers. This guide is intended to help you get the most out of the R mailing lists, and to avoid embarrassment.
see anything addressing this.
Is this the right place to ask?
Kind Regards,
Joseph Wood
------------------------------
[R-pkg-devel] Package Etiquette
3 messages · Killick, Rebecca, Robert M. Flight
Regarding still wanting to copy functions situation, I did this for my knitrProgressBar PKG, as it makes the progress R6 object from dplyr a first class citizen of the PKG, and dplyr has a lot of dependencies that I didn't want to force just to use their pre-existing progress bar. Robert On Wed, Sep 12, 2018, 7:09 AM Killick, Rebecca <r.killick at lancaster.ac.uk> wrote:
To add my two-pence regarding duplication.
I think this is a judgement call.
If the functionality would be precisely the same and for the same
situations then there are some instances where you would still want to
duplicate but generally probably not. An example would be where the
function is small and easy to code but depending on the existing package
would bring a large reverse dependency that you don't want to have.
Thanks,
Rebecca
----------------------------------------------------------------------
Message: 1
Date: Sat, 8 Sep 2018 21:11:46 -0400
From: Joseph Wood <jwood000 at gmail.com>
To: r-package-devel at r-project.org
Subject: [R-pkg-devel] Package Etiquette
Message-ID:
<CAKDcrSjmmt_VsZk=
KjiyfPCnbTfmOTOzwLfcsepTpRPnWRPj+g at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi all,
I?m a new developer and this is my first post. I have a question regarding
package development with regards to duplication of functionality. I read
the posting guide (https://www.r-project.org/posting-guide.html) and
didn?t
R: Posting Guide: How to ask good questions that prompt ...<
https://www.r-project.org/posting-guide.html> www.r-project.org Posting Guide: How to ask good questions that prompt useful answers. This guide is intended to help you get the most out of the R mailing lists, and to avoid embarrassment. see anything addressing this. Is this the right place to ask? Kind Regards, Joseph Wood [[alternative HTML version deleted]] ------------------------------ [[alternative HTML version deleted]] ______________________________________________ R-package-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Of course, if you do truly decide to *copy* a function from another package, make sure everything is licensed appropriately and the authors given attribution! -Robert
On Wed, Sep 12, 2018, 8:09 AM Robert M. Flight <rflight79 at gmail.com> wrote:
Regarding still wanting to copy functions situation, I did this for my knitrProgressBar PKG, as it makes the progress R6 object from dplyr a first class citizen of the PKG, and dplyr has a lot of dependencies that I didn't want to force just to use their pre-existing progress bar. Robert On Wed, Sep 12, 2018, 7:09 AM Killick, Rebecca <r.killick at lancaster.ac.uk> wrote:
To add my two-pence regarding duplication.
I think this is a judgement call.
If the functionality would be precisely the same and for the same
situations then there are some instances where you would still want to
duplicate but generally probably not. An example would be where the
function is small and easy to code but depending on the existing package
would bring a large reverse dependency that you don't want to have.
Thanks,
Rebecca
----------------------------------------------------------------------
Message: 1
Date: Sat, 8 Sep 2018 21:11:46 -0400
From: Joseph Wood <jwood000 at gmail.com>
To: r-package-devel at r-project.org
Subject: [R-pkg-devel] Package Etiquette
Message-ID:
<CAKDcrSjmmt_VsZk=
KjiyfPCnbTfmOTOzwLfcsepTpRPnWRPj+g at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi all,
I?m a new developer and this is my first post. I have a question regarding
package development with regards to duplication of functionality. I read
the posting guide (https://www.r-project.org/posting-guide.html) and
didn?t
R: Posting Guide: How to ask good questions that prompt ...<
https://www.r-project.org/posting-guide.html> www.r-project.org Posting Guide: How to ask good questions that prompt useful answers. This guide is intended to help you get the most out of the R mailing lists, and to avoid embarrassment. see anything addressing this. Is this the right place to ask? Kind Regards, Joseph Wood [[alternative HTML version deleted]] ------------------------------ [[alternative HTML version deleted]] ______________________________________________ R-package-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel