-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
license file should be deleted #7
Comments
My understanding (from here) is that you can include the type of license in the DESCRIPTION, but it can also indicate the presence of a LICENSE file. That is the issue I'm seeing when I do I'm going to update DESCRIPTION to also include the LICENSE file, as provided by the TEOS org. By the way, my R settings that produce the license note are:
and the output of
|
Commit 57d9efb has an updated DESCRIPTION and LICENSE. Let me know if you think this is sensible. It can always be reverted. |
That looks excellent to me. It seems short enough that whoever decides on acceptability should be able to figure it out quite quickly. The danger in doing something other than GPL-2 or other standard is that some special permissions might be required to get it into the CRAN stream. But maybe the "|" operator is sufficient, in any case. |
Thanks. I think I see why we get different results. Somehow, the I don't know what's doing on, because when I do We should probably figure out how the two of us are getting different behaviour on |
In case it's of any use, below is the Makefile portion that I use for gsw. The inference of "most recent" is done by a whacky pipe string that may be brittle if version-numbering is altered.
|
Oh I see why we're seeing different things -- it's an ID10T error. I've been doing
which checks the directory, rather than the built tarball. If I build and check as you do, I now get the following note:
I just deleted some other comments about DESCRIPTION errors, because I had not pulled the latest version which you had already fixed. |
(This follows some direct emails between coauthors. I'm marking the assignee as CR since he noticed some problems with build warnings, related to the license. I don't see such problems when I build, so it will be easier for CR to see if any new problems arise when we remove the LICENSE file.)
I just read in the R docs the following. So we cannot include the
LICENSE
file.The text was updated successfully, but these errors were encountered: