** Summary changed: - Hardy package for tovid doesn't makemenu, makexml etc. into user's path + Hardy package for tovid doesn't place makemenu, makexml etc. into user's path
** Description changed: Binary package hint: tovid As described at http://ubuntuforums.org/showthread.php?t=830499, the Debian package for tovid available in the repositories on Hardy installs makemenu, makexml, makedvd and makevcd (and possibly other scripts) into /usr/share/tovid, but these utilities are not placed into the user's - path. The only way to call them is to give the full path; i.e., - simplying typing "makemenu" returns a "command not found" error, but + path. The only way to call them is to give the full path; i.e., simply + typing "makemenu" returns a "command not found" error, but "/usr/share/tovid/makemenu" works. This was not the case on Gutsy, so I think it's a bug. To make things worse, tovidgui (installed from the same repository) fails because it complains about not being able to find makemenu, etc., because it expects them to be in the user's path and they're not. Symlinking the programs in /usr/share/tovid to /usr/bin works around the problem, but that solution is not obvious to non-technical users. Unless there's an obscure logic behind not placing makemenu, etc. in the user's path, why don't we fix this? I'm using amd64; I'm not sure if this problems exists with the i386 package as well. -- Hardy package for tovid doesn't place makemenu, makexml etc. into user's path https://bugs.launchpad.net/bugs/252026 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
