Skip to content

Make cabal check warn if copyright field doesn't have current year #780

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

Closed
bos opened this issue May 24, 2012 · 1 comment
Closed

Make cabal check warn if copyright field doesn't have current year #780

bos opened this issue May 24, 2012 · 1 comment

Comments

@bos
Copy link
Contributor

bos commented May 24, 2012

(Imported from Trac #790, reported by guest on 2011-01-15)

Quite a few packages being uploaded on Hackage have 2010 as the copyright year, probably because developers forgot to update the year. As an example, see http://hackage.haskell.org/package/turni-2011.1.15 which was uploaded in 2011, but puts the copyright as 2010 (that's just the first I encountered, but there are loads).

I suggest cabal check should warn if copyright doesn't have the current year in the field.

@bos
Copy link
Contributor Author

bos commented May 24, 2012

(Imported comment by @BenMachine on 2011-01-15)

Copyright fields can in general contain an arbitrary string (or frequently, no string at all) so I imagine it being tricky to parse a year out of it reliably unless we also standardised the format. Think about things like (c) 2006-9 John Smith, 2009-10 Martha Jones.
Plus there are plenty of packages that aren't the original work of the uploader (e.g. forks, maintainerships, cabalizations, etc.), in which case it might be inappropriate to update the copyright field.

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

No branches or pull requests

1 participant