Package Details: execute-git 19-1

Git Clone URL: https://aur.archlinux.org/execute-git.git (read-only, click to copy)
Package Base: execute-git
Description: Opens exe and bat files as if they were native
Upstream URL: https://gitlab.com/es20490446e/exeCute
Keywords: dos dosbox emulator exe exeCute windows wine
Licenses: GPL3
Conflicts: execute
Provides: execute
Submitter: es20490446e
Maintainer: None
Last Packager: es20490446e
Votes: 1
Popularity: 0.034369
First Submitted: 2019-04-03 09:31
Last Updated: 2019-11-15 07:38

Latest Comments

1 2 Next › Last »

es20490446e commented on 2019-11-17 09:26

Could you provide examples that I can test where things would go worse without those?

librewish commented on 2019-11-16 18:55

add exe-thubnailer and wine-installer as deps

es20490446e commented on 2019-11-15 07:39

Review now.

es20490446e commented on 2019-11-14 23:23

This will be fixed within a week.

coderobe commented on 2019-11-14 21:52

automation scripts aside, the pkgbuild needs fixing. you can do the automation part later if you so wish...

es20490446e commented on 2019-11-14 21:51

As per the orphan request, I thought I said I will fix it.

coderobe commented on 2019-11-14 21:22

Right, so even if all your scripts work correctly, pulling the source and acquiring the pkgver are not atomically tied to each other - you may generate invalid metadata with this due to TOCTOU...

Please fix your PKGBUILDs to follow the common pkgbuild style, removing these hacks.

es20490446e commented on 2019-11-14 21:14

Ummm... now that you say it most likely yes. I will add testing that to my todo list , and report back here if I see any problem with that. Otherwise I will update all the packages accordingly.

lfleischer commented on 2019-11-14 20:20

I don't understand what the problem with using an external tool is. This external tool can use exactly the same logic to update $pkgver in the PKGBUILD and push a new PKGBUILD to the AUR.

es20490446e commented on 2019-11-14 19:51

Bottom line is:

  • These decisions are experimental and incomplete. I haven't brought a discussion about them because it's too soon for that, and the only way to figure them out is to publish them in a controlled manner.

  • A group can agree with the overall result of the work, but its implementation consist of hundreds of small details that only the implementer knows. Discussing all of those is impracticable.