Search Criteria
Package Details: cmake-init 0.41.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/cmake-init.git (read-only, click to copy) |
---|---|
Package Base: | cmake-init |
Description: | The missing CMake project initializer |
Upstream URL: | https://github.com/friendlyanon/cmake-init |
Keywords: | CMake utility |
Licenses: | GPL3 |
Submitter: | muio |
Maintainer: | muio |
Last Packager: | muio |
Votes: | 4 |
Popularity: | 0.000242 |
First Submitted: | 2021-09-20 16:14 (UTC) |
Last Updated: | 2025-01-14 20:15 (UTC) |
Latest Comments
muio commented on 2024-03-31 17:08 (UTC)
@vedranmiletic thank you.\ I tried to make changes you suggested and here's what I'm going to do going forward:
notice how the directories are different.
There's also this warning that pops up in the package() step:
looking at the suggested link, I didn't find any obvious way of fixing it.
vedranmiletic commented on 2024-03-26 10:18 (UTC)
@muio This did not work very well and I forgot the build step. Roughly:
vedranmiletic commented on 2024-03-26 10:10 (UTC)
@muio there is no pyproject.toml so it is hard to follow the guidelines.
Assuming source set to https://github.com/friendlyanon/$pkgname/archive/refs/tags/v$pkgver.tar.gz
The package() function should be something like
cd $pkgname-$pkgver cd package python setup.py install
carlosal1015 commented on 2023-12-31 19:41 (UTC)
The package should be named as cmake-init-bin
tocic commented on 2023-12-29 04:01 (UTC)
I believe you shouldn't use
pip
at all. See https://wiki.archlinux.org/title/Python_package_guidelines.Check out these links. In the end it might be an upstream issue as well (in that case it's worth to contact the author here).
muio commented on 2023-12-28 20:54 (UTC) (edited on 2023-12-28 20:54 (UTC) by muio)
Okay. Should I revert it back to the old method? If so, while I do know how to prevent pip from complaining that it is being ran as root by passing
--root-user-action=ignore
to it, I don't know how to fix the other two. Any ideas?tocic commented on 2023-12-28 08:16 (UTC)
Well, yes, it fixed the build warnings since we don't build the package now. But I believe 1) we can't use the python files directly, i.e. use the package as a library; 2) maybe the package name should have the suffix
-bin
to illustrate that it was "built" by the upstream; 3) we definitely need to update thepkgrel
field, see https://wiki.archlinux.org/title/PKGBUILD#pkgrel.muio commented on 2023-12-28 00:37 (UTC) (edited on 2023-12-28 00:38 (UTC) by muio)
Just switched it to the Github .pyz releases instead of .whl files released on pypi. Less headaches and no more warnings. @tocic see if it's fixed on your end.
tocic commented on 2023-12-11 06:59 (UTC)
The warnings are still present in the 0.39.0 version. Could you please take a look at them? BTW, I can adopt this package if you want.
tocic commented on 2023-11-13 07:05 (UTC)
There are some warnings when building the 0.38.0 version: