Search Criteria
Package Details: unrpyc 2:2.0.2-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/unrpyc.git (read-only, click to copy) |
---|---|
Package Base: | unrpyc |
Description: | A ren'py script decompiler |
Upstream URL: | https://github.com/CensoredUsername/unrpyc |
Licenses: | MIT |
Submitter: | Stary2001 |
Maintainer: | dcelasun |
Last Packager: | dcelasun |
Votes: | 7 |
Popularity: | 0.044657 |
First Submitted: | 2015-08-12 14:31 (UTC) |
Last Updated: | 2024-09-02 08:16 (UTC) |
Dependencies (2)
- python (python37AUR, python311AUR, python310AUR)
- python-setuptools (make)
Latest Comments
1 2 Next › Last »
fenuks commented on 2024-09-06 07:39 (UTC)
I don't say it's an issue, but arguably it complicates/uglifies the version number. Personally, I would remove when a new major version of python is about to be released, but that's my opinion. Yes, it would show as a downgrade, but just once, when you are forced to rebuild manually to get package working.
dcelasun commented on 2024-09-06 07:31 (UTC) (edited on 2024-09-06 07:47 (UTC) by dcelasun)
That's not the problem. If I remove it, everyone who currently has it installed with
epoch=2
will see it as a downgrade when they try to install a new version. Anyway, it's not an issue.fenuks commented on 2024-09-06 07:19 (UTC)
I got it build without it, so I had to rebuild. I think you could remove it just before Arch packages new major version of python, since package will have to be rebuilt to make it work again.
dcelasun commented on 2024-09-06 05:00 (UTC)
You can't remove epoch once added, because it would register as a downgrade. Why do you care?
fenuks commented on 2024-09-05 21:21 (UTC)
Is there a good reason to keep using
epoch
in PKGBUILD?dcelasun commented on 2024-09-02 07:57 (UTC)
@fenuks because the tagged versions were broken with latest renpy for a long, long time. I'll update soon.
fenuks commented on 2024-09-02 07:36 (UTC)
@dcelasun Why do you use git to build non-git package, when it is possible to build it from source archive?
mirh commented on 2024-02-25 12:24 (UTC)
Well, du-uh... After years of nothingness, they decided to update the main repo just now (and the other dev branches were deleted).
dcelasun commented on 2024-01-18 12:06 (UTC)
OK, switched to that fork.
mirh commented on 2024-01-17 23:57 (UTC)
Well, the python 2 branches shouldn't even be considered in this day and age. On top of that, after some cursory comparison of the patchsets, py3_v1.2.0_dev is undoubtedly the most modern and comprehensive.
1 2 Next › Last »