Search Criteria
Package Details: devilspie2 0.45-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/devilspie2.git (read-only, click to copy) |
|---|---|
| Package Base: | devilspie2 |
| Description: | A window matching utility, allowing the user to perform scripted actions on windows as they are created. |
| Upstream URL: | https://www.nongnu.org/devilspie2/ |
| Licenses: | GPL-3.0-or-later |
| Submitter: | larchunix |
| Maintainer: | larchunix |
| Last Packager: | larchunix |
| Votes: | 37 |
| Popularity: | 0.81 |
| First Submitted: | 2012-05-25 20:53 (UTC) |
| Last Updated: | 2024-10-25 20:24 (UTC) |
Latest Comments
1 2 3 Next › Last »
smw commented on 2024-10-20 08:44 (UTC)
Is the upstream repository being maintained? This fork appears to be much more active: https://github.com/dsalt/devilspie2
yan12125 commented on 2020-08-12 16:17 (UTC)
Partially my fault - I didn't really check larchunix's commits until lua 5.4 enters [extra]. If the patch is correctly applied when lua 5.4 is still in [staging], users will be able to rebuild whenever they wish.
Regarding aurutils - I saw there was a proposal to bump pkgrel with an option [1], which seems suitable for these cases.
[1] https://github.com/AladW/aurutils/pull/725
eschwartz commented on 2020-08-09 03:35 (UTC) (edited on 2020-08-09 03:36 (UTC) by eschwartz)
It's gross to have packages get reinstalled in-place to fix updated dependencies, and breaks AUR helpers like aurutils (which use pacman -Syu + custom repo rather than pacman -U ./<file>). While there is no rule saying you need to bump pkgrel just to get people to recompile against new versions of lua/perl/python/$language, I'd personally do it, because there's nothing wrong with doing it. It's not like most rebuilds are expensive.
The point is moot since the commit which applied the patch to this package to fix it on lua 5.4, occurred 14 hours after lua 5.4 got moved from testing to extra.
There is no valid world in which it was correct to skip a pkgrel bump in the commit "Actually apply FTBS patch", which applied code changes to make the package build correctly in tandem with the lua 5.4 update that required the patch.
yan12125 commented on 2020-08-08 01:47 (UTC)
Yep a rebuild is needed after lua is upgraded, The problem is, users with testing repos enabled need to rebuild earlier than those who don't. If pkgrel is bumped once lua 5.4 entered [testing] repo, whose who don't use testing repos will need to rebuild devilspie2 for lua 5.4 again whe lua 5.4 enters [extra] repo. Similarly, if pkgrel is bumped once lua 5.4 entered [extra], users with testing repos enabled may get another unneeded rebuild. As a result, I think rebuild should be handled by users, not AUR package maintainers.
Kewl commented on 2020-08-07 16:33 (UTC)
devilspie stopped working after the lua update, the rebuild of the package was quite necessary to me, I would not call it "useless"
yan12125 commented on 2020-08-07 15:05 (UTC)
I agree what @larchunix said below - "without bumpimg pkgrel to avoid useless rebuild". PKGBUILDs on AUR reflect how a package is built, not what the built package is.
Kewl commented on 2020-08-06 18:45 (UTC)
we need a bump in pkgrel
yan12125 commented on 2020-08-06 15:18 (UTC)
Thanks! I can confirm it works.
larchunix commented on 2020-08-06 07:46 (UTC)
@yan12125: Oops, it should be ok this time...
yan12125 commented on 2020-08-06 02:30 (UTC)
Hi larchunix, thanks for adding the patch, but looks like the patch is not actually applied in PKGBUILD. Could you add it?
1 2 3 Next › Last »