Just an FYI, I simply took the ebuild for helixplayer-bin-0.3.0.71 and bumped it up for the latest (at the time) binary for 0.3.0.77. I've been running realone for sometime and this was my first crack at the newer helixplayer. Much nicer and Linux friendly. Thanks for making 0.3.0.71 available. Reproducible: Always Steps to Reproduce: 1. modify ebuild for 0.3.0.77 2. download binary for 0.3.0.77 to /usr/portage/distfiles 3. emerge helixplayer-bin -u
From what I understand, .96 is out at this point. An update would be spiffy.
actually, .116.
There will be a alpha build on May 18th...
Should be all set. I bumped it to revision 0.3.0.124 which is the May 16 snapshot. I'll keep this bug open until the May 18th Alpha release.
Right on, thanks. One issue though. I looked at the URL in the ebuild to get tbe bin, and stuck it in /usr/portage/distfiles and made sure it was readable by portage, and it still says: # emerge helixplayer-bin Calculating dependencies ...done! >>> emerge (1 of 1) media-video/helixplayer-bin-0.3.0.124 to / !!! hxplay-0.3.0.124-linux-2.2-libc6-gcc32-i586.tar.bz2 not found in /usr/portage/distfiles. !!! media-video/helixplayer-bin-0.3.0.124 has fetch restriction turned on. !!! This probably means that this ebuild's files must be downloaded !!! manually. See the comments in the ebuild for more information. !!! The following are listed in SRC_URI for helixplayer-bin: !!! hxplay-0.3.0.124-linux-2.2-libc6-gcc32-i586.tar.bz2 Did I miss something?
Well, I have good and bad news. The good news is that the Alpha release (https://helixcommunity.org/project/showfiles.php?group_id=154&release_id=198) no longer requires a click through and has real source code. The bad new is that the build is not your nice ./configure; make, it's a custom build environment and script. It may take me a while to work through it. However, I may make a 0.3.0.123 (the alhpa release), ebuild that won't have fetch restrictions. That seems like a plus.
I have submitted Alpha version 0.3.0.123 to the tree. I have also masked 0.3.0.71 and 0.3.0.124 since they require fetch restrictions. FieldySnuts, I'm really not sure what the problem is that you are running into. I would recommend trying 0.3.0.123. Especially since it doesn't have fetch restrictions on. If you are behind a firewall, you will still have to download the new tar ball until it propogates to the gentoo mirrors.
