Package Details: mkdocs 1.6.0-1

Git Clone URL: https://aur.archlinux.org/mkdocs.git (read-only, click to copy)
Package Base: mkdocs
Description: Project documentation with Markdown
Upstream URL: https://www.mkdocs.org
Keywords: generator static website wiki
Licenses: BSD
Conflicts: python-mkdocs
Provides: mkdocs
Submitter: None
Maintainer: AlphaJack
Last Packager: AlphaJack
Votes: 34
Popularity: 0.30
First Submitted: 2015-06-11 18:21 (UTC)
Last Updated: 2024-04-24 23:12 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

vedranmiletic commented on 2022-09-29 08:53 (UTC)

Thanks for updating to 1.4.0, but it fails to build with:

==> Starting build()...
* Getting dependencies for wheel...
running egg_info
creating mkdocs.egg-info
writing mkdocs.egg-info/PKG-INFO
writing dependency_links to mkdocs.egg-info/dependency_links.txt
writing entry points to mkdocs.egg-info/entry_points.txt
writing requirements to mkdocs.egg-info/requires.txt
writing top-level names to mkdocs.egg-info/top_level.txt
writing manifest file 'mkdocs.egg-info/SOURCES.txt'
reading manifest file 'mkdocs.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching '*.mustache' under directory 'mkdocs'
warning: no files found matching '*.mo' under directory 'mkdocs'
warning: no previously-included files matching '__pycache__' found under directory '*'
warning: no previously-included files matching '*.py[co]' found under directory '*'
adding license file 'LICENSE'
writing manifest file 'mkdocs.egg-info/SOURCES.txt'

ERROR Missing dependencies:
wheel
==> ERROR: A failure occurred in build().
Aborting...
greška: neuspješan build 'mkdocs-1.4.0-1':
greška: neuspješan build na paketima: mkdocs-1.4.0-1

jiggak commented on 2021-08-17 20:09 (UTC)

Missing dependency on python-dateutil

AlphaJack commented on 2021-06-30 23:35 (UTC)

@ainola I have just submitted the merge requests

ainola commented on 2021-06-18 16:17 (UTC)

The wiki on AUR submission guidelines [1] mentions using replaces(). In general, though, AUR users are expected to keep up with their packages as they're external to the repositories.

If you want me to mass move everything let me know when you're ready.

[1] https://wiki.archlinux.org/title/AUR_submission_guidelines#Rules_of_submission

AlphaJack commented on 2021-06-17 09:11 (UTC)

@ainola

Am I missing something?

Not really, in your opinion what would be the best way to perform this mass package renaming?
Perhaps adding "provides=(mkdocs-foo python-mkdocs-foo)" and "conflicts=(python-mkdocs-foo)" to the new "mkdocs-foo" package will make the transition painless and conflict-free for end users?

AlphaJack commented on 2021-06-15 18:44 (UTC)

Thanks, I have added it

wjhandley commented on 2021-06-15 10:49 (UTC)

This is currently missing a dependency on python-pyyaml-env-tag

ainola commented on 2021-06-11 22:32 (UTC)

Hi, AlphaJack:

The name "mkdocs" appears to be correct in accordance to the rules on naming Python packages [1]. As this is a standalone program and not a library closely related to the Python ecosystem, it sounds to me like it should remain as is and that python-mkdocs should instead be merged into this package. Indeed, looking through the "getting started" guide on mkdocs' website suggests that the only interaction with mkdocs is as a utility, much like Hugo. Is this correct?

I see that there are many "modules" for mkdoc that have a python- prefix as well; I would also argue that they should simply be "mkdoc-foo" rather than "python-mkdoc-foo" as, again, there's no real relationship to the Python ecosystem.

Am I missing something?

[1] https://wiki.archlinux.org/title/Python_package_guidelines#Package_naming

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »