https://bugzilla.redhat.com/show_bug.cgi?id=2227502
Tom Rix <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Doc Type|--- |If docs needed, set a value Status|NEW |ASSIGNED CC| |[email protected], | |[email protected] Assignee|[email protected] |[email protected] --- Comment #2 from Tom Rix <[email protected]> --- There are at least 2 other cmark's.. what's one more ? It would be good if cmark-gfm.spec was consistent with cmark.spec, with additions to the description on why a user would want to use this version over the the other. It's github's fork. Why would someone want to use this ? Looking for something simple like .. 'Needed to run this or that github workflow .. ' added to the description. I looked at houdini. Would it be worth its own package ? Review the houdini source and the list of files that are claimed to have an MIT license. It looks like cmark and cmark-gfm's use a derivative of houdini's buffer.* The copyright boiler plate from houdini has been stripped from the cmark version. /* * Copyright (C) the libgit2 contributors. All rights reserved. * * This file is part of libgit2, distributed under the GNU GPL v2 with * a Linking Exception. For full terms see the included COPYING file. */ gpl v2 != mit And stripping copyrights is not good. This license and copyright problem should be resolved in the upstream. If it can't, then add gpl v2 to the license list in the rpm, with a detail explanation on the provenance of the buffer files. This also effects the other cmark's in fedora. -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2227502 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202227502%23c2 _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
