pytrec-eval-terrier: update packages

docs/packages/pytrec-eval-terrier.yaml

@@ -18,3 +18,4 @@ versions:
   - filename: pytrec_eval_terrier-0.5.10-cp314-cp314t-manylinux_2_34_riscv64.manylinux_2_39_riscv64.whl
     sha256: 6a5a88397e6d05c70b0a26648be1b22c0246548b3b7da5f813cea6b06f13b8cb
     requires-python: '>=3'
+- version: 0.5.11

patches/pytrec-eval-terrier/0.5.11/0001-Add-LICENSE.trec_eval-for-the-vendored-trec_eval-source.patch

@@ -0,0 +1,56 @@
+From 0ecf629011edc089211fe49a815619fb8c84aa1b Mon Sep 17 00:00:00 2001
+From: Ludovic Henry <git@ludovic.dev>
+Date: Thu, 10 Sep 2026 08:06:34 +0200
+Subject: [PATCH] Add LICENSE.trec_eval for the vendored trec_eval C sources
+
+setup.py compiles trec_eval's C sources straight into the pytrec_eval_ext
+extension (sources=['src/pytrec_eval.cpp'] + TREC_EVAL_SRC, where
+TREC_EVAL_SRC lists every *.c in the trec_eval submodule/tarball) -- it is
+the functional core, not an optional or system-linked dependency. Upstream
+pins this to trec_eval v9.0.8 (REMOTE_TREC_EVAL_URI in setup.py, and the
+trec_eval submodule here is pinned to the same tag), and the built wheel
+carries only pytrec_eval-terrier's own MIT LICENSE (confirmed via the
+released sdist's PKG-INFO: `License-File: LICENSE`, nothing else) -- the
+same as every other platform wheel upstream's own CI publishes.
+
+v9.0.8's individual .c files still carry Chris Buckley's original 2008
+per-file header ("Permission is granted for use and modification of this
+file for research, non-commercial purposes"). But usnistgov/trec_eval
+added a repository-wide LICENSE.md in 2024 (first shipped in v10.0) whose
+text explicitly states it covers "the code for the original trec_eval, up
+to version 9" and relicenses the whole project, Buckley's code included,
+as NIST public-service software: "You may use, copy, and distribute copies
+of the software in any medium... You may improve, modify, and create
+derivative works." That statement, from the project's current copyright
+holders (Buckley's original copyright plus Ian Soboroff's NIST-employee
+modifications), is the authoritative, current statement of terms -- more
+so than a per-file comment two major versions stale. This patch ships that
+text (verbatim from github.com/usnistgov/trec_eval's current LICENSE.md)
+as LICENSE.trec_eval at the project root, where setuptools' default
+license_files glob (LICEN[CS]E*) picks it up automatically alongside the
+project's own LICENSE, same mechanism as the python-mecab-ko port's
+LICENSE.mecab-ko.
+
+Upstream-Status: To upstream [blocked: this port may only touch riseproject-dev/python-wheels]
+---
+ LICENSE.trec_eval | 7 +++++++
+ 1 file changed, 7 insertions(+)
+ create mode 100644 LICENSE.trec_eval
+
+diff --git a/LICENSE.trec_eval b/LICENSE.trec_eval
+new file mode 100644
+index 0000000..145e551
+--- /dev/null
++++ b/LICENSE.trec_eval
+@@ -0,0 +1,7 @@
++The code for the original trec_eval, up to version 9, are Copyright (C) 2008 Chris Buckley.  Significant modifications have been done by Ian Soboroff as an employee of NIST.  Other modifications and ongoing support are by Ian Soboroff and other contributors on https://github.com/usnistgov/trec_eval.  trec_eval is now made available under the following license.
++
++NIST-developed software is provided by NIST as a public service. You may use, copy, and distribute copies of the software in any medium, provided that you keep intact this entire notice. You may improve, modify, and create derivative works of the software or any portion of the software, and you may copy and distribute such modifications or works. Modified works should carry a notice stating that you changed the software and should note the date and nature of any such change. Please explicitly acknowledge the National Institute of Standards and Technology as the source of the software.
++
++NIST-developed software is expressly provided "AS IS." NIST MAKES NO WARRANTY OF ANY KIND, EXPRESS, IMPLIED, IN FACT, OR ARISING BY OPERATION OF LAW, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND DATA ACCURACY. NIST NEITHER REPRESENTS NOR WARRANTS THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT ANY DEFECTS WILL BE CORRECTED. NIST DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OF THE SOFTWARE OR THE RESULTS THEREOF, INCLUDING BUT NOT LIMITED TO THE CORRECTNESS, ACCURACY, RELIABILITY, OR USEFULNESS OF THE SOFTWARE.
++
++You are solely responsible for determining the appropriateness of using and distributing the software and you assume all risks associated with its use, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and the unavailability or interruption of operation. This software is not intended to be used in any situation where a failure could cause risk of injury or damage to property. The software developed by NIST employees is not subject to copyright protection within the United States.
+\ No newline at end of file
+-- 
+2.50.1 (Apple Git-155)
+