Arch Linux User Repository

@Musikolo: Thanks a lot! Regarding the service menus: It would have been nice if there were some more opinions. Maybe it's just me who likes the user preferences settings better...

@BertiBoeller: Removed unneeded lib32-qt3 dependency for x86_64 architecture. Thanks for your notice. @Everybody: In order to find a solution the different opinions regarding whether KDE service menus should or shouldn't be installed globally, I have included a question in the build script asking you for this. By default, they will be installed. So, if you do not want them to be installed, simply reply No to the question. I hope everybody is happy with these changes. Regards.

@Musikolo: Regarding the service menus: I think this depends on the preferences of the user. If you have lots of programs which install entries in the service menu it can become cluttered and you can't disable the "Edit" and compare with file menu entries. But it's your package so it's up to your preference what you chose as default. It should be save to remove the "lib32-qt3" dependency. I've installed Beyond Compare without that dependency and it seems to run just fine. Namcap doesn't complain also.

@fnine: Thanks for your notice. There was a bug while building the package on i686 architecture, but the new PKGBUILD file sorts it out. The issue didn't affect x86_64 users, so no changes for them. Regards.

I just ran into this. Package installation fails with "==> ERROR: A failure occurred in build()". Reason is that you hide the error message, but not the error :-) Adding "|| true" to the kde_context_menu line fixes this. Regards, /alex

@BertiBoeller: I'm aware about the error caused while trying to find the 'menu.ini' file, but I didn't find any problem because of this: the service menus were generated fine. That's why the script hides this error by using 2> /dev/null. If find anything wrong with this, please, let me know. Regarding the fact of installing the service menus globally, I think when you install a package as root (or with sudo) the purpose is to put it at the service of all the users of that PC. Otherwise, the user should do his own local installation, rather than relying on a global one. Besides, I don't see anything wrong in making the service menus available to everyone as the binary of the package is also available to everyone: would it make any sense to put the binaries available to all users and not to do the same with the service menus? I don't think... Regards.

Hello, thanks for the package! If you're installing bcompare for the first time the part with the ServiceMenus will fail because the script looks for a file called 'menu.ini' in '~/.beyondcompare' and '/usr/lib/beyondcompare'. If you haven't run Beyond Compare and saved your settings the file won't exist and the build of the package will fail. On a multi user system it probably wouldn't be a good idea to make these configurations global anyway. Regards.

@adam.bococz: Included system KDE service menus, so now there is no need to have ~/.kde4/share/kde4/services/ServiceMenus directory. They are installed at /usr/share/kde4/services/ServiceMenus instead. Regards.

It could be nice if you could add execution of cript which creates right-click actions in KDE, script is located in package /usr/lib/beyondcompare/kde_contect_menu, before you run it you must create dir called ServiceMenus in ~/.kde4/share/kde4/services/ otherwise it fails... BTW. ScooterSoftware provides that deb package as 30-day trial, after that period you have to enter serial number... when I install that deb on ubuntu, it works as trial, so twopumpchump was right that it is unexpected behaviour.

Updated to version 3.3.4. Regards.