Package Details: bcompare-kde4 5.0.3.30258-2

Git Clone URL: https://aur.archlinux.org/bcompare.git (read-only, click to copy)
Package Base: bcompare
Description: KDE 4 service menus for Beyond Compare 5.
Upstream URL: https://www.scootersoftware.com
Keywords: compare diff
Licenses: custom
Groups: utility
Conflicts: bcompare-kde
Replaces: bcompare-kde
Submitter: Musikolo
Maintainer: Musikolo
Last Packager: Musikolo
Votes: 100
Popularity: 0.075516
First Submitted: 2011-07-27 22:54 (UTC)
Last Updated: 2024-10-26 16:23 (UTC)

Dependencies (2)

Required by (1)

Sources (1)

Pinned Comments

Musikolo commented on 2024-08-25 07:07 (UTC) (edited on 2024-10-16 03:55 (UTC) by Musikolo)

You can build the last version of Beyond Compare v4 I packaged (4.4.7.28397) by doing this:

git clone https://aur.archlinux.org/bcompare.git/
cd bcompare
git checkout dcf8794f1301c9213558b2583a956c04cf2a2135
makepkg -crs

Since you have a license for v4, you might be interested in looking at the upgrade policy at https://www.scootersoftware.com/kb/upgradepolicy .

I hope it helps!

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 22 Next › Last »

Musikolo commented on 2015-11-19 06:01 (UTC)

Updated to 4.1.2.20720: - bcompare-gnome renamed as bcompare-nautilus - bcompare-xfce renamed as bcompare-thunar - added bcompare-nautilus and bcompare-mate packages - yaourt issues should be gone (not tested though) Enjoy!

Wesley_Chan commented on 2015-11-18 02:28 (UTC)

@Musikolo, @blueyed, Please change Line 48 to cd "bcompare-${pkgver}" to enable yaourt style installation. sha256sum for 4.1.2.20720 32-bit: bdf5f3c32782c60516554fcbfa34f84f3e46ea0757bda2f1a4cd8670fb748864 64-bit: 7e820508f5fbc9fe97e2f1b5e7fe020cd213399f011c9808e78a3d9eafb4913f Thank you.

blueyed commented on 2015-11-12 01:13 (UTC)

"bcompare-gnome" fails to install with "pacaur -S bcompare-gnome". This is likely true for all extra packages (see similar reports for yaourt): ==> Validating source files with sha256sums... bcompare-4.1.1.20615.x86_64.tar.gz ... Passed ==> Extracting sources... -> Extracting bcompare-4.1.1.20615.x86_64.tar.gz with bsdtar ==> Starting prepare()... /tmp/pacaurtmp-daniel/bcompare/PKGBUILD: line 48: cd: bcompare-gnome-4.1.1.20615: No such file or directory ==> ERROR: A failure occurred in prepare().

Wesley_Chan commented on 2015-10-26 08:12 (UTC)

@Musikolo, I've never tried to use Thunar in KDE. My apology. I have no problem in naming the packages. Here's context menus for Cinnamon and MATE2/3. Tested. http://pastebin.com/Y8B1vGyC But in the case of MATE, I think ScooterSoftware made a mistake. The directory should be "extension2" rather than "extension3". A pull request has been made to the GitHub. To make it work, a small patch can be applied to install.sh. But I suppose we should wait for the upstream. Hope this helps.

Musikolo commented on 2015-10-23 04:39 (UTC)

@Wesley_Chan: I'm open to any suggestion, of course, but you cannot use Thunar in KDE unless you have all Xfce core libs installed. So, in the end, every window manager has its our file explorer and every file explorer depends on the window manager it was created for. On top of that, it's true that for Gnome and Xfce, we could use bcompare-nautilus and bcompare-nemo names, but this is not the case for KDE, because the service menus are not for Dolphin only, they are for any KDE-compatible file explorer. So, I don't see the point in using the file explorer name in some cases and the window manager in others. I think that by using the window manager it's (reasonably) clear what its package is intended for. Lastly, there used to be some people complaining about the fact that service menus were installed all the time and they didn't want to have them at all. Having all service menus in one package is not as flexible as having it in separate packages. You could find people that wants to have service menus for Nautilus, but don't want to have it for Nemo. For this reason, I truly believe that having everything separate is the best option. Does it make sense to you?

Wesley_Chan commented on 2015-10-23 01:23 (UTC) (edited on 2015-10-23 01:59 (UTC) by Wesley_Chan)

@Musikolo, I'm sorry but shouldn't it be bcompare-thunar, bcompare-nemo, bcompare-nautilus etc.? I mean, you can definitely use nemo as file manager in Gnome, or thunar in KDE. It should be named after FM, rather than DE. What do you think? P.S.: And what is a person supposed to do if he uses both nemo and thunar? He couldn't possibly install both the packages. So please re-consider separating them. Thanks. P.S. again: Oh, I can see those separate packages are only installing menu entries. Sorry. Still, I personally think it's better all-in-one. The latest version support more than that now. I'll try to do an update. Thanks.

Musikolo commented on 2015-10-21 04:39 (UTC)

@petrovo: You are right. It should be fixed now. Thanks for your support! ;-)

petrovo commented on 2015-10-20 14:05 (UTC)

The problem really is that the package is created and in the file "/usr/bin/bcompare", 1st line, is into the path "BC_LIB" added the installation directory before "/lib/beyondcompare". Correctly be only: BC_LIB=/lib/beyondcompare I can't find where it is in the scripts.

Salzi commented on 2015-10-20 06:14 (UTC)

I was unable to install bcompare-kde-4.1.1.20615 with yaourt: /tmp/yaourt-tmp-salzi/aur-bcompare-kde/./PKGBUILD: line 48: cd: bcompare-kde-4.1.1.20615: No such file or directory The installation with makepkg was successful.

Musikolo commented on 2015-10-20 05:26 (UTC)

@petrovo: Could you please try with makepkg instead of yaourt?

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 22 Next › Last »