Package Details: pip2pkgbuild 0.5.0-2

Git Clone URL: https://aur.archlinux.org/pip2pkgbuild.git (read-only, click to copy)
Package Base: pip2pkgbuild
Description: Create PKGBUILD files for Python modules fetched with PIP
Upstream URL: https://github.com/wenLiangcan/pip2pkgbuild
Keywords: packaging pip pkgbuild python
Licenses: MIT
Conflicts: python2-pip2pkgbuild
Submitter: wenLiangcan
Maintainer: RubenKelevra
Last Packager: RubenKelevra
Votes: 25
Popularity: 0.007117
First Submitted: 2015-09-15 12:49 (UTC)
Last Updated: 2024-08-09 05:27 (UTC)

Latest Comments

1 2 3 4 Next › Last »

gesh commented on 2024-12-23 14:52 (UTC)

Note: Package needs to be rebuilt for Python 3.13 (a bump to pkgrel suffices)

RubenKelevra commented on 2024-08-08 07:53 (UTC)

@gesh you're welcome

gesh commented on 2024-08-07 19:41 (UTC)

OK, fair enough, thanks for explaining

RubenKelevra commented on 2024-08-07 19:09 (UTC)

@wenLiangcan thanks! Make sure to hit "Flag out of date" the next time. That's easier to spot than a comment notification :)

RubenKelevra commented on 2024-08-07 19:08 (UTC)

@gesh sorry but I still don't see the benefit using git to do the download.

RubenKelevra commented on 2024-08-07 19:04 (UTC)

@gesh yeah I read that - it's not true.

The automatic will select --compile-bytecode=1.

This may be fine for a *-git package, but makes no sense for regular packages.

--compile-bytecode=1 leaves stuff like assertions and docstrings intact, which have no use, unless you run a debugger, which I doubt will anyone do on .pyc files anyway.

Hope this helps.

gesh commented on 2024-08-06 18:55 (UTC)

BTW, any reason you have --compile-bytecode=2 in package()? The wiki says it shouldn't be necessary

gesh commented on 2024-08-06 18:44 (UTC)

source can't change (because of the checksum), so the same version is always the same version.

FYI -- when using git+$url.git#tag=$pkgver makepkg can compute a checksum off of the tarball generated by git archive --format tar. The more relevant tradeoff is that this format pulls in the entire git history, which could be significant for other projects (in this project's case, the total size is ~300K, which is IMO not worth microoptimizing). But whatever works for you.

wenLiangcan commented on 2024-08-06 14:54 (UTC)

Hi guys, FYI the upstream code is updated, and sorry for lacking of maintenance of this package.

RubenKelevra commented on 2024-08-05 07:26 (UTC) (edited on 2024-08-05 07:27 (UTC) by RubenKelevra)

@gesh wrote:

Thanks for updating this, I'm still looking over the changes. BTW, it may be worth using git+$url.git#tag=$pkgver as the source rather than the github tarball --

I'm using in in other cases where there's no tar ball available But using tar balls is usually preferential, as the source can't change (because of the checksum), so the same version is always the same version.

1 2 3 4 Next › Last »