Search Criteria
Package Details: python-mammoth 1.9.1-4
Package Actions
Git Clone URL: | https://aur.archlinux.org/python-mammoth.git (read-only, click to copy) |
---|---|
Package Base: | python-mammoth |
Description: | Convert Word documents (.docx files) to HTML |
Upstream URL: | https://github.com/mwilliamson/python-mammoth |
Licenses: | MIT |
Conflicts: | mammoth |
Provides: | mammoth |
Submitter: | envolution |
Maintainer: | envolution |
Last Packager: | envolution |
Votes: | 0 |
Popularity: | 0.000000 |
First Submitted: | 2024-12-16 18:23 (UTC) |
Last Updated: | 2025-06-12 02:23 (UTC) |
Dependencies (12)
- python (python37AUR)
- python-cobbleAUR
- python-build (make)
- python-installer (make)
- python-setuptools (make)
- python-wheel (make)
- python-funkAUR (check)
- python-preciselyAUR (check)
- python-pyflakes (python-pyflakes-gitAUR) (check)
- python-pytest (check)
- python-spur (check)
- python-tempmanAUR (check)
Latest Comments
envolution commented on 2025-05-29 06:48 (UTC)
@vitaliikuzhdin i take your point - I've added conflicts+provides=mammoth which hopefully addresses either scenario - appreciate the report
vitaliikuzhdin commented on 2025-05-28 21:28 (UTC)
@envolution, I've seen CLI+library Python packages named after the CLI tool, with
python-$name
added to theprovides=()
andconflicts=()
arrays. Since the library name is only relevant to maintainers who understand it's a virtual dependency, and users will search specifically for the name of the CLI tool, I think that's a reasonable option to consider. But you're right, I don't believe this is a formal guideline.envolution commented on 2025-05-28 21:18 (UTC)
@vitaliikuzhdin it's also a library not just a CLI - if you see the packages that depend on it you'll see it's used as a library for markitdown - which is the reason I brought it to AUR
AFAIK there's no rules about naming conventions for library+cli, but when a package is installed as a python module that others may 'require'; naming it python-* seems to be the best practice
vitaliikuzhdin commented on 2025-05-28 20:52 (UTC)
If this is a CLI tool that just happens to be written in Python, shouldn't the name of the package be just
mammoth
?