Skip to content
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

3rd clause of BSD refers to "linode-netint" #44

Closed
paravoid opened this issue Sep 5, 2019 · 4 comments · Fixed by #47
Closed

3rd clause of BSD refers to "linode-netint" #44

paravoid opened this issue Sep 5, 2019 · 4 comments · Fixed by #47

Comments

@paravoid
Copy link

paravoid commented Sep 5, 2019

The third clause of the attached BSD license reads:

  • Neither the name of linode-netint nor the names of its
    contributors may be used to endorse or promote products derived from
    this software without specific prior written permission.

Presumably this is a copy/paste error, rather than this software actually deriving from linode-netint (if it is, then the appropriate copyright should also be added).

Given this has already been licensed for ~4 years using a 3rd clause that is not terribly effective, I'd recommend to just relicense to a 2-clause BSD rather than changing the reference to "flock".

@paravoid
Copy link
Author

Ping? I'd like to package this for Debian and would prefer if this was resolved (and a 0.7.2 cut) before than after :) Thanks for all of your efforts!

@theckman
Copy link
Member

@paravoid Apologies. Finally realizing how messed up my email filters were and I missed this for a super long time.

Are you still intending to package this for Debian?

@theckman
Copy link
Member

@paravoid v0.7.3 was cut in reaction to this issue. You may also want to wait to v0.8.0, if you intend to package this, as that would be AIX support (from #40).

@theckman
Copy link
Member

@paravoid v0.8.0 has been released to include AIX support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants