Package Details: vvv-bin 1.5.0-1

Git Clone URL: (read-only, click to copy)
Package Base: vvv-bin
Description: VVV (Virtual Volumes View) is an application that catalogs the content of removable volumes like CD and DVD disks for off-line searching
Upstream URL:
Licenses: GPL2
Submitter: Muflone
Maintainer: Muflone
Last Packager: Muflone
Votes: 4
Popularity: 0.007110
First Submitted: 2019-12-29 17:18 (UTC)
Last Updated: 2023-11-05 19:28 (UTC)

Latest Comments

Muflone commented on 2020-06-28 14:46 (UTC) (edited on 2020-06-28 14:47 (UTC) by Muflone)

Hi @djmattyg007, thank you for your message but I don't agree with all of your points:

1) in Arch Linux /usr/bin/sh is a /usr/bin/bash symlink, there's no differences at all in replacing the shebang

2) the exec line would close the starting script, resulting in the caller program to believe the program was closed

3) conflicting with an unexisting program is non-sense. a help in building vvv from sources will be more useful and this package could be dropped

4) variables surrounded with ${ } IMHO is a good thing everyone should ever use, regardless with the specific benefits it gives with other cases

5) this is a binary package that upstream author has built using gtk2, there's no way to not to use gtk2 libraries as they are dinamically linked to the executable file (ldd VVV-1.4.0-x86_64/vvv). See also #3

djmattyg007 commented on 2020-06-20 12:35 (UTC)

I also have a couple of recommendations for the PKGBUILD:

  1. The PKGBUILD should conflict with the package 'vvv', even though it doesn't exist yet. There's no need to wait for someone to come along and actually create that package in order to do so, and you'll help people by just doing it now.

  2. The PKGBUILD is unnecessarily difficult to read because the variable '${_pkgname}' has been used everywhere, which is almost four times as long as the string it represents ('vvv'). Given the name of the package is unlikely to change very often (if ever), it generally doesn't make a lot of sense to use a variable for such a thing.

  3. Is gtk2 actually a hard dependency? The official website claims it uses wxWidgets, and when I install VVV on Windows I don't see any GTK-related DLLs getting installed. It would be good to avoid packages depending on gtk2 given it'll go away eventually, just like python2.

djmattyg007 commented on 2020-06-20 12:30 (UTC)

I have a couple of recommendations for the launcher script that gets copied into /usr/bin:

  1. bash is compulsory on Arch because pacman has a hard dependency on it. All PKGBUILD files need to be valid bash scripts. Therefore, there's little to be gained by using /bin/sh as the shebang. Just use /bin/bash. You won't have to deal with compatibility with other shells.

  2. Prepend the last line of the script (the line that actually launches the program) with exec. By not doing so, the bash process is left running for no real reason. All it does is interfere with proper signal handling and other monitoring tasks that a launcher (such as my desktop environment applications menu) may want to perform.

RTRT commented on 2020-01-01 05:04 (UTC)

I'm using zsh. It worked like a charm after removing the directory!

Thank you!

Muflone commented on 2019-12-31 18:11 (UTC) (edited on 2019-12-31 18:14 (UTC) by Muflone)


do you have the .vvv directory in your home folder? If so, try to remove it

are you using bash as your shell?

RTRT commented on 2019-12-31 17:00 (UTC)

Hi. It doesn't launch correctly here.

An unexpected error has occurred. Here is a description of the error:

IBPP::SQLException Context: Database::Connect Message: isc_attach_database failed

SQL Message : -901 can't format message 13:99 -- message file /media/disco2/firebird-2.0.7-installed/firebird.msg not found

Engine Code : 335544382 Engine Message : Missing configuration file: /home/USER/.vvv/firebird/firebird.conf, exiting