@CyberConan Changed (along with some minor fixes). Thanks!
Search Criteria
Package Details: veetle 0.9.17+-4
Package Actions
| Package Base: | veetle |
|---|---|
| Description: | Official Player (using the 0.9.17plus version for better x86_64 and pulseaudio support) |
| Upstream URL: | http://www.veetle.com |
| Category: | multimedia |
| Licenses: | |
| Submitter: | metak |
| Maintainer: | Tido.com |
| Last Packager: | None |
| Votes: | 50 |
| First Submitted: | 2010-03-03 19:04 |
| Last Updated: | 2013-08-26 07:34 |
Dependencies (20)
Required by (0)
Sources
Latest Comments
Comment by migrev
Comment by CyberConan
Better results with x64 and pulseaudio replacing "vlcori --aout oss" --> "vlcori --alsadev 0"
http://www.lziegler.com/wordpress/?p=108
Comment by dejavu
@fcpt:
I have now disowned the package, because I don't use it anymore.
Take the original one. ;-)
Anonymous comment
I made a veetle system wide install,
https://aur.archlinux.org/packages.php?ID=55546
Anonymous comment
If you want to remove the requirement to run "ln -s /opt/veetle ~/.veetle_vlc" per user:
- replace in libveetle-player-plugin* the string '%s/.veetle_vlc/vlc' by '/opt/veetle_vlc/v_'
- rename vlc to v_
Comment by American_Jesus
Add optdepends=('lib32-libpulse') for audio support on x86_64 systems with pulseaudio
Comment by dejavu
Done...
I haven't unset the strip option yet.
But now you get only your i686 stuff ;-)
and x86_64 get their x86_64 stuff...
Comment by dieghen89
Yes, i686...
Comment by dejavu
Ah ok, are you using i686?
I'll fix that...
Comment by dieghen89
Here i get an error:
-> Rimozione dei simboli non necessari dai binari e dalle librerie in corso...
/usr/bin/strip:./usr/lib/mozilla/plugins/libveetle-player-plugin-x86_64.so: File format not recognized
using options=(!strip) solves :)
Comment by dejavu
New Veetle Version
New PGKBUILD
New Maintainer
- added a lot of new dependencies. ;-)
- now only a symlink is needed and has to be done only once.
Thanks to dieghen89 for maintaining it until now.
Comment by dieghen89
Yeah you can pick up all my PKGBUILD, put my name in Contributor and write yours in Mainteiner ;)
Comment by dejavu
Wow that was fast. ;-)
Is it okay, if I will take some parts of your PGKBUILD?
Comment by dieghen89
Now you can adopt it :)
Comment by dejavu
Yeah if it's no problem for you then I would take the package...
I have done my new package now...
Comment by dieghen89
I don't use daily this package, and i don't follow his (very slow) develop....If you want, i can leave the package so you can pick it up....
Comment by dejavu
Hey,
I also want to use this package...
So I have some suggestions, if you don't like it then I have to do it on my own and have to add a second package to aur. ;-)
1. It would be nice if you could use the 0.9.17+ package from the forum of veetle. The link can also be found on "our" forum.
The reason is: Good x64 support and much smaller size.
2. Suggestion: Can't you use symlinks (suggest to user who installs the package) like @tri6791 suggested instead of copy. Sure we need one subdirectory with write access in veetle directory. But thats also possible with a symlink to the tmp folder?!
Comment by dieghen89
Hi tri6791, you can try...if someone not root has to write in that folder you can change manually the chown it...
Comment by tri1976
can I "ln -s /usr/share/veetle/vlc ~/.veetle_vlc" instead of copy? Does it write anything to ~/.veetle_vlc directory?
Comment by toketin
nothing for x86_64 it doesn't work, neither the manual installation :|
Comment by nTia89
i've installed it but firefox doesn't recognize its plugins..... how i can solve?
Anonymous comment
Does this package work on x86_64?
Comment by 3ED_0
Two problems:
1) I have audigy2, not some integrated shit, but in this soft I don't have sound.. ;[
>>>>> [00000263] alsa audio output error: write failed (Zły argument) <<<<<
2) This doesn't install their files to /usr
BTW. I will waiting to good version, but by now I don't want it in my PC. :)
Comment by dieghen89
Hi guys! I've modified the pkgbuild to install files only in /usr folder....After the install the user has to moove a folder in his home, as says the .install file...
PKGBUILD:
http://aur.pastebin.com/cLjQURzZ
veetle.install:
http://aur.pastebin.com/UYPAFQLp
Anonymous comment
The veetle plugin will not work in Firefox 64-bit. Not through this AUR package and not with a manual install.
Comment by skottish
You're installing executable plug-ins in the user's home directory? This is a gigantic security issue. I wouldn't run this package ever. If fact, no one should install this package as it is right now if they value their personal data.
Anonymous comment
veetle x64 plugins still not work.
Anonymous comment
After installing the package .mozilla is owned by root. I don't think that's correct :)
Comment by celilo
All plugins fail to register on Arch_64 / firefox-3.6.3 (namoroka).
Comment by othello
about:plugins shows only veetle-core as an installed plugin. veetle-player and veetle-broadcast are both absent. (32-bit FF 3.6 and Chromium, if that matters.)
Comment by tri1976
I have to change arch=('i686 x86_64') to arch=('i686' 'x86_64') in order for it to recognize 32bit or 64bit system.
Anonymous comment
veetle & firefox told me under x86_64 that I havent the right version.
Comment by metak
why do I then get md5sum to be ba307af10d770628a5e20951ad3f0bd3? when i put in 7fd8d488056864ecc94102ba6516f6ab it doesn't work... :)
Anonymous comment
7fd8d488056864ecc94102ba6516f6ab
Comment by metak
sorry about that... :)
Anonymous comment
I've md5 checksum error! :(
Anonymous comment
Thank you =D
Comment by metak
I've sent a report to veetle team about this issue and they released a new version of 0.9.17 for linux which I've tried and it works fine.. :)
Comment by metak
When I run chromium-browser %U from console and try to play channel on veetle site I get error that I'm missing libmpcdec.so.3 and libfaad.so.0.
So a temporary solution would be to create symbolic links for those two files... and I've modefied PKGBUILD to do that...
I know that's not "the right way" of doing but at least it works...
Anonymous comment
"firefox-branded 3.6.2" crashes with this new version :(