Search Criteria
Package Details: python-jsmin 3.0.1-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/python-jsmin.git (read-only, click to copy) |
---|---|
Package Base: | python-jsmin |
Description: | JavaScript minifier |
Upstream URL: | https://pypi.org/pypi/jsmin |
Licenses: | MIT |
Submitter: | rafaelff |
Maintainer: | Score_Under |
Last Packager: | Score_Under |
Votes: | 22 |
Popularity: | 0.000022 |
First Submitted: | 2016-05-27 12:04 (UTC) |
Last Updated: | 2022-12-11 09:29 (UTC) |
Dependencies (2)
- python (python37AUR, python311AUR, python310AUR)
- python-setuptools (make)
Latest Comments
1 2 Next › Last »
spaceslug commented on 2022-10-02 09:35 (UTC)
According to the jsmin project page, python2 is no longer supported.
And1G commented on 2022-10-02 08:40 (UTC)
Is it possible to split this in a python2 and a python3 variant? So python3 users would not need to build a complete python2 from source.
audeoudh commented on 2021-11-02 17:49 (UTC)
Just bumping the version works for me (Python3 only, not tested Python2):
@@ -5,4 +5,4 @@ pkgname=('python-jsmin' 'python2-jsmin') pkgbase=python-$_name -pkgver=2.2.2 -pkgrel=3 +pkgver=3.0.0 +pkgrel=1 pkgdesc="JavaScript minifier" @@ -13,3 +13,3 @@ makedepends=('python-setuptools' 'python2-setuptools') source=("https://pypi.org/packages/source/${_name:0:1}/$_name/$_name-$pkgver.tar.gz") -md5sums=('00e7a3179a4591aab2ee707b3214e2fd') +sha256sums=('88fc1bd6033a47c5911dbcada7d279c7a8b7ad0841909590f6a742c20c4d2e08')
Luk313 commented on 2021-09-22 15:58 (UTC)
Hello, thanks a lot for this package. Would it be possible to upgrade to jsmin 3.0 please? I'am having problems to upgrade other packages that require jsmin 3.0. Thanks a lot ! :)
djmattyg007 commented on 2021-01-03 02:55 (UTC)
Even if I was to forcibly rebuild this package with
aur sync --rebuild
, it wouldn't alert machines that there is a package update to download. I'd also have to forcibly reinstall the package on every machine I have it installed on.The alternative is to just change a single character in a single file so that literally everybody can benefit from this update.
rafaelff commented on 2019-12-09 12:24 (UTC)
@djmattyg007: I don't think "the whole point of the pkgrel flag is to trigger rebuilds". Its main use is to implement "fixes and additional features" to the PKGBUILD, according to https://wiki.archlinux.org/index.php/PKGBUILD#pkgrel; Devs/TUs from official repositories use pkgrel bump with rebuild to force update because users of those binary packages wouldn't have this fix available with the new dependencies otherwise, which is a different scenario.
Have you tried using
--rebuild
flag ofaur sync
? It forces a package currently available in the repository to be rebuilt and added to the local customrepository.djmattyg007 commented on 2019-12-09 10:03 (UTC)
Literally the whole point of the pkgrel flag is to trigger rebuilds in cases such as these. It's honestly disappointing to see such a high level of pushback against changing a single character in a single file.
djmattyg007 commented on 2019-12-09 09:57 (UTC)
@rafaelff I use aurutils as my AUR helper. It involves running a full package repository recognised by pacman on my machine.
https://github.com/AladW/aurutils
Rebuilding packages with the same version number isn't really something it was built to do. It relies on AUR maintainers properly playing their part in maintaining a package, and that includes bumping the pkgrel to automatically trigger a rebuild for things such as C library changes or new editions of python, just like what would happen in the official repositories.
The fact is that it probably takes a lot less effort for maintainers to change a single character in their PKGBUILDs, rather than making every single person who's built and installed your package manually check their python library files to see if anything has been left behind during the upgrade.
rafaelff commented on 2019-12-08 10:15 (UTC) (edited on 2019-12-08 10:17 (UTC) by rafaelff)
In time, I recommend users of Python packages in AUR to check "/usr/lib/python3.7/site-packages/" for directories. Directories in there might be from Python packages that were built with Python3.7, which should present problems with Python3.8. If anything is found under that directory, package rebuild is recommended.
1 2 Next › Last »