Package Base Details: bcompare

Git Clone URL: (read-only, click to copy)
Keywords: compare diff
Submitter: Musikolo
Maintainer: Musikolo
Last Packager: Musikolo
Votes: 83
Popularity: 0.94
First Submitted: 2011-07-27 22:54
Last Updated: 2020-03-01 00:12

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

Salzi commented on 2016-03-22 07:35

Can not update to the new version. Get the error:

makepkg: invalid option '--pkg'
==> ERROR: Makepkg was unable to build bcompare.

I installed only bcompare without an optional package.

Musikolo commented on 2016-03-19 05:10

Updated to version 4.1.5-21031.


Musikolo commented on 2016-03-10 03:23

Updated to version 4.1.4-20978.


Musikolo commented on 2015-12-24 23:52

@vith: You should have kde4-config if you want to use bcompare-kde package. In that case, you should have kdelibs available, as shown in the next command:

[musikolo@MyPC ~]$ pacman -Qo /usr/bin/kde4-config
/usr/bin/kde4-config is owned by kdelibs 4.14.15-1

If you aren't interested in KDE at all, please just ignore the error altogether because the script it's assuming the file existence when checking KDE version. It seems to be a small bug, but nothing be worried about.

Please, let me know if anything else is needed.

Thanks for you feedback.

vith commented on 2015-12-24 13:26

Seems to work fine but I saw this weird message when installing with `pacaur -S bcompare`. Is that expected?

==> Starting package_bcompare()... line 184: kde4-config: command not found
Please place the following in your .bashrc or .cshrc (etc.)
export PATH=/tmp/pacaurtmp-vith/bcompare/src/install/bin:$PATH
Executable is /tmp/pacaurtmp-vith/bcompare/src/install/bin/bcompare

Musikolo commented on 2015-11-19 06:01

Updated to
- 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)


Wesley_Chan commented on 2015-11-18 02:28

@Musikolo, @blueyed,

Please change Line 48 to

cd "bcompare-${pkgver}"

to enable yaourt style installation.

sha256sum for
32-bit: bdf5f3c32782c60516554fcbfa34f84f3e46ea0757bda2f1a4cd8670fb748864
64-bit: 7e820508f5fbc9fe97e2f1b5e7fe020cd213399f011c9808e78a3d9eafb4913f

Thank you.

blueyed commented on 2015-11-12 01:13

"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- ... Passed
==> Extracting sources...
-> Extracting bcompare- with bsdtar
==> Starting prepare()...
/tmp/pacaurtmp-daniel/bcompare/PKGBUILD: line 48: cd: bcompare-gnome- No such file or directory
==> ERROR: A failure occurred in prepare().

Wesley_Chan commented on 2015-10-26 08:12


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.

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 But I suppose we should wait for the upstream.

Hope this helps.

Musikolo commented on 2015-10-23 04:39

@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?