Hello,

On Sun 15 Dec 2024 at 10:52pm -08, Xiyue Deng wrote:

> To look at it from complexity point of view, installing CHANGELOG.org as
> changelog requires the following minimum change:
>  1) Not included CHANGELOG.org in d/docs (which now only includes
>  NEWS.org),
>  2) Override dh_installdocs to install CHANGELOG.org as changelog,
> while using a symlink from changelog to CHANGELOG.org requires:
>  1) Include CHANGELOG.org in d/docs,
>  2) Add linking to changelog in d/links,
>  3) Compress CHANGELOG.org by overriding dh_installdocs as it's not
>  compressed by default and it's required for changelog.gz,
>  4) Add a lintian override for that what-I-think-is-a-false-positive
>  tag.
> So the former wins here, and I have implemented it now in Salsa.

Hmm, commit a2c1074 on salsa is otherwise okay but still does the
symlinking, did you forget to push?

> [ On the other hand, I think using CHANGELOG.org is becoming a common
>   practice in many ELPA packages and it should be considered a supported
>   format for changelog.  I'll probably follow-up on this in another bug
>   to see if this would be acceptable, so that step 2-4 of the latter
>   won't be required.  What would be a good place to file such a wishlist
>   bug? ]

Again, file extensions don't matter.
Writing CHANGELOG in Org format is indeed common; there is nothing wrong
with installing it without its file extension.  So, I don't think there
is anywhere that has a bug.

> Ack.  It looks like policy 12.5 does say copyright information should be
> verbatim, however as we can group the copyright holder spanning multiple
> years, it becomes "not-verbatim" then.  Oh well, guess nothing is
> perfect.

Yes, good point.

>> You'll need a copy of the entire EPL-2.0, per Policy 12.5.
>>
>
> Lintian warns about not including CC-BY-SA-4.0 full text but doesn't
> warn about EPL-2.0.  Anyway, I think including the full text is the safe
> bet and this has been done.
>
> PTAL.

Rather than relying on Lintian, just take a look under
/usr/share/common-licenses and see what's there :)

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature

Reply via email to