
Code: Select all
ebuild bmpx-svn.ebuild digest
!!! media-sound/bmpx-svn does not follow correct package syntax.

You should call it bmpx-0.9999.ebuild - for example:slack---line wrote:ebuild bmpx-svn.ebuild digest
!!! media-sound/bmpx-svn does not follow correct package syntax.
Code: Select all
# ebuild bmpx-0.9999.ebuild digest
>>> Generating the digest file...
>>> Generating the manifest file...
<<< bmpx-0.9999.ebuild
<<< files/digest-bmpx-0.9999
>>> Computed message digests.
You are right with it, but isnt version 1.0 too far from now? In BMPx roadmap I see 0.14, 0.15. For today and next few weeks (maybe months/years) is 0.9999 allrightPaulBredbury wrote:No, because then version 1.0 would be "more recent" than svn, which is wrong.radfoj wrote:0.9999.ebuild



!!! All ebuilds that could satisfy "bmpx" have been masked.
!!! One of the following masked packages is required to complete your request:
- media-sound/bmpx-0.12.9-r1 (masked by: package.mask)
# Martin Schlemmer <azarah@gentoo.org (01 Mar 2006)
# Have multiple issues, and 0.13 release have segfaults (fixed in svn, but
# _only_ after 0.13 release although the fact was known before the 0.13
# release). Either way, no bugfix release was made, and upstream was very
# agro about the fact that I did not still want to add the 0.13 with known
# issues. I dont want to maintain this anymore as working with upstream
# needs a lot of patience and diplomacy, and I do not have the energy any
# longer. I will remove it from the tree if nobody steps up shortly to
# take over.
- media-sound/bmpx-0.12.9-r2 (masked by: package.mask)
- media-sound/bmpx-0.12.9 (masked by: package.mask)
- media-sound/bmpx-0.12.6.1 (masked by: package.mask)

it relies on gst-plugins 0.10.### which are mostly ~ARCH. However, the killer is it relies on dev-libs/glib-2.10.1 which is part of the GNOME 2.13/14 release. I dont know how much it is going to break my system but I am emerging this glib even though I am using GNOME 2.12 just so I can use BMPx[/quote]Gentoo Linux
Gentoo doesn't have a maintainer for BMPx at the moment, so here is the latest ebuild, followed by simple instructions:
/etc/make.conf
PORTDIR_OVERLAY="/usr/local/portage"
Execute following:
mkdir -p /usr/local/portage/media-sound/bmpx
echo 'media-sound/bmpx' >> /etc/portage/package.unmask
echo 'media-sound/bmpx' >> /etc/portage/package.keywords
cd /usr/local/portage/media-sound/bmpx
wget http://unaffiliated.unk.fi/media-sound/ ... -r2.ebuild
ebuild bmpx-0.14_rc2-r2.ebuild digest
emerge -av bmpx

It's actually just RC2 ebuild, not final release..Naib wrote:Well latest version has been released. V0.14.
After all the feasco with V0.13 hopefully we can all move on
Since BMPx isn't being "supported" by Gentoo anymore the nice people at BMPx have made an ebuild
http://bmpx.beep-media-player.org/site/Downloads

beep-media-player-2 executes the GUI, check this:Naib wrote:good to here
there doesn't seem to be a GUI anymore???
When I goto run bmpx, it doesn't exist all that does exist is beep-media-player-2 which is CLI-only
where can I get a GUI-client?

Code: Select all
beep-media-player-2 -v
bmpx 0.14_rc2
Copyright (c) 2005-2006 BMPx development team
Built the Sat Mar 18 15:59:13 CET 2006 on Linux 2.6.15-gentoo-r7 (i686) with:
* X11 Session Management
* Configuration backend: Gconf
* Amazon album cover support
* Core GUI (Winamp 2.x skinning engine)Code: Select all
/usr/libexec/beep-media-player-2-bin --no-log
BMPx-Message: BMPx STARTED [2006-03-18 17:33:08] PID [30068]
BMPx-Message: Socket path is /tmp/bmpx-root
BMPx-Message: ping_socket.c:121: Connection error: Po³±czenie odrzucone
BMPx-Message: loader.c:78: flow plugin: libflow_linear.so
BMPx-INFO: Success loading plugin.
BMPx-Message: loader.c:78: flow plugin: libflow_shuffle.so
BMPx-INFO: Success loading plugin.
BMPx-Message: loader.c:78: container plugin: libcontainer_pls.so
BMPx-INFO: Success loading plugin.
BMPx-Message: loader.c:78: container plugin: libcontainer_query.so
BMPx-INFO: Success loading plugin.
BMPx-Message: loader.c:78: container plugin: libcontainer_xspf.so
BMPx-INFO: Success loading plugin.
BMPx-Message: loader.c:78: container plugin: libcontainer_folder.so
BMPx-INFO: Success loading plugin.
BMPx-Message: loader.c:78: container plugin: libcontainer_m3u.so
BMPx-INFO: Success loading plugin.
BMPx-Message: loader.c:78: transport plugin: libtransport_file.so
BMPx-INFO: Success loading plugin.
BMPx-Message: loader.c:78: transport plugin: libtransport_http.so
BMPx-INFO: Success loading plugin.
BMPx-Message: loader.c:78: transport plugin: libtransport_cdda.so
BMPx-INFO: Success loading plugin.
BMPx-Message: loader.c:78: transport plugin: libtransport_query.so
BMPx-INFO: Success loading plugin.
BMPx-Message: sm.c:282: Unable to open SM connection: SESSION_MANAGER environment variable not defined
BMPx-Message: Plik z obrazem "/usr/share/bmpx/icons/themes" nie zawiera danych
BMPx-Message: Plik z obrazem "/usr/share/bmpx/icons/themes" nie zawiera danych
BMPx-Message: Plik z obrazem "/usr/share/bmpx/icons/themes" nie zawiera danych
BMPx-Message: Plik z obrazem "/usr/share/bmpx/icons/themes" nie zawiera danych
BMPx-Message: Plik z obrazem "/usr/share/bmpx/icons/themes" nie zawiera danych
BMPx has crashed. If you suspect a bug, please consult http://bmpx.beep-media-player.org/site/Reporting_bugs
Przerwane

Log won't be needed afterall.. This is a bug, with gconf backend in RC2. Your options are:kion wrote:I have the same problem as Naib.
If the log from emerge will be helpfull I will send it to forum, but it is huge.

Well I had to doSamuliSuominen wrote:...

Yes i'm more or less affiliated with BMPx devs, and developers have though about following f.d.o specs in ~/.config too. I added this to my ebuilds just some hours ago,Naib wrote:
Well I had to do
USE="-gnome" emerge bmpx
to get the GUI (I dont want to put that into /etc/portage/package.use yet.
it is a shame that isn't fixed
SamuliSuominen you afiliated with the Dev's of BMPx?
If so a couple of points
1) BPMx or BMP-2 as it seems to be known makes a ~/.bmp-2.0 the Freedesktop spec states config should go into ~/.config
SMEG, fraveman, last.fm are all using it. It would be useful and more tidy IF BMPx also used this
2) internet radio streams don't seem to work
I tend to use the stream from D&Bforum but BMPx doesn't accept it
http://www.dnbradio.com/hi.pls
don't mind the music, just my type when in the mood for it
3) I decided to check out last.fm (to get some live streams) but it doesn't seem to be accepting, I have signed up and last.fm player works, but offloading to BMPx doesn't
4) the memory usage seems a bit high. I have had it hitting 140meg!
Even when it is working fine Audacity uses 40meg with BMPx using 60meg (this is more reasonalble I guess)
Code: Select all
./configure --prefix=/usrCode: Select all
./configure --prefix=/usr --sysconfdir=/etcCode: Select all
./configure --prefix=/usr --sysconfdir=/usr/local/etc --with-gconf-schema-file-dir=/etc/gconf/schemas

Yep yep, I've taken care of that in my ebuilds.deadchip wrote:Guys just a little info on the GConf backend:
The warning from the topic (as drac posted above) doesn't come from the fact that it's less stable or buggy than the XML backend, but because it's "harder" to get it done right.
While it's enough for the basic installation of BMPx when you use the XML-file backend to pass just (for example):
you MUST pass a valid sysconfdir variable as well for the GConf backend, e.g.Code: Select all
./configure --prefix=/usr
so that the schemas get installed right (and of course that sysconfdir must point to 'the' sysconfdir where GConf stores it schemas, on most systems that would be /etc/gconf/schemas).Code: Select all
./configure --prefix=/usr --sysconfdir=/etc
This is nothing unusual with BMPx, it's like that with every app that uses GConf and installs GConf schemas.
Furthermore, if you need, for some reason, to point BMPx's general sysconfdir to somewhere else than /etc (although currently nothing else in BMPx would make use of that anyway), then you can do, for example (this is just an example; please read the full sentence before you take this as a real advice):
Code: Select all
./configure --prefix=/usr --sysconfdir=/usr/local/etc --with-gconf-schema-file-dir=/etc/gconf/schemas
Bottom line is: When you use the GConf backend, you must make sure the schemas get installed into the right place. Now some of you maybe don't even really know what a GConf schema actually is, and there's nothing wrong with that, but that's why i said: "When in doubt, use the XML-file backend"
tnx,SamuliSuominen wrote:...
We could make a skin repository on our site; just send in skins (preferrably some BMPx "branded" skins if you have them, i know there are a few floating around but i couldn't get hold of them yet), or just your favorite skin, and we'll put it online (if it's not too ugly LOL)Naib wrote:apart from that pritty good, pitty no skin came with it,