Re: Patch: Run BMP independently of XMMS

--=-lCtu4vud9B4v51MEbkOu
Content-Type: multipart/mixed; boundary="=-MMzCVS4uXGOAGFvHoEWt"


--=-MMzCVS4uXGOAGFvHoEWt
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, 2003-11-19 at 17:38, Rafal Zawadzki wrote:
> Dnia 2003-11-18 15:35, U=C5=BCytkownik Chong Kai Xiong napisa=C5=82:
> > 'sup all!
> >=20
> > Here's my first patch contribution. It simply changes the local socket
> > filename BMP uses so that BMP can run independently of XMMS.
>=20
> What about some programs like xmms-shell? Will they still be usable?

No, I'm looking into it. I had simply renamed the socket so I could run
BMP with XMMS still opened.
=20
Currently, I'm adding a 'XMMS compatibility mode' aka xmms_compat to BMP
(as a command line switch and app. preference).=20

In xmms_compat mode, BMP will listen on 2 sockets (BMP's and XMMS')
Programs like xmms-shell should work with BMP running in this mode.

BTW, my patch doesn't work right as well - BMP doesn't start if XMMS is
started first.  Here's corrected patch if anyone is still interested.
Please note that it does NOT add xmms_compat.


--=20
Chong Kai Xiong
aka 'Descender'



--=-MMzCVS4uXGOAGFvHoEWt
Content-Disposition: attachment; filename=socket-patch.diff
Content-Type: text/x-patch; name=socket-patch.diff; charset=UTF-8
Content-Transfer-Encoding: base64

LS0tIGJtcC9iZWVwL2NvbnRyb2xzb2NrZXQuYwkyMDAzLTExLTE0IDAxOjI3OjI1LjAwMDAwMDAw
MCArMDgwMA0KKysrIGJtcC1kZXNjZW5kZXIvYmVlcC9jb250cm9sc29ja2V0LmMJMjAwMy0xMS0x
OCAxMzowMDoyOC4wMDAwMDAwMDAgKzA4MDANCkBAIC02MCw3ICs2MCw3IEBADQogCQlmb3IgKGkg
PSAwOzsgaSsrKQ0KIAkJew0KIAkJCXNhZGRyLnN1bl9mYW1pbHkgPSBBRl9VTklYOw0KLQkJCWdf
c25wcmludGYoc2FkZHIuc3VuX3BhdGgsIDEwOCwgIiVzL3htbXNfJXMuJWQiLA0KKwkJCWdfc25w
cmludGYoc2FkZHIuc3VuX3BhdGgsIDEwOCwgIiVzL2JlZXBfJXMuJWQiLA0KIAkJCQkgICBnX2dl
dF90bXBfZGlyKCksIGdfZ2V0X3VzZXJfbmFtZSgpLCBpKTsNCiAJCQlpZiAoIXhtbXNfcmVtb3Rl
X2lzX3J1bm5pbmcoaSkpDQogCQkJew0KLS0tIGJtcC9saWJiZWVwL2JlZXBjdHJsLmMJMjAwMy0x
MS0xNCAwMToyODo0MS4wMDAwMDAwMDAgKzA4MDANCisrKyBibXAtZGVzY2VuZGVyL2xpYmJlZXAv
YmVlcGN0cmwuYwkyMDAzLTExLTE5IDA2OjQ2OjE4LjAwMDAwMDAwMCArMDgwMA0KQEAgLTI3Niw3
ICsyNzYsNyBAQA0KIAkJc3RvcmVkX3VpZCA9IGdldHVpZCgpOw0KIAkJZXVpZCA9IGdldGV1aWQo
KTsNCiAJCXNldHVpZChldWlkKTsNCi0JCWdfc25wcmludGYoc2FkZHIuc3VuX3BhdGgsIDEwOCwg
IiVzL3htbXNfJXMuJWQiLCBnX2dldF90bXBfZGlyKCksIGdfZ2V0X3VzZXJfbmFtZSgpLCBzZXNz
aW9uKTsNCisJCWdfc25wcmludGYoc2FkZHIuc3VuX3BhdGgsIDEwOCwgIiVzL2JlZXBfJXMuJWQi
LCBnX2dldF90bXBfZGlyKCksIGdfZ2V0X3VzZXJfbmFtZSgpLCBzZXNzaW9uKTsNCiAJCXNldHJl
dWlkKHN0b3JlZF91aWQsIGV1aWQpOw0KIAkJaWYgKGNvbm5lY3QoZmQsIChzdHJ1Y3Qgc29ja2Fk
ZHIgKikgJnNhZGRyLCBzaXplb2YgKHNhZGRyKSkgIT0gLTEpDQogCQkJcmV0dXJuIGZkOw0K

--=-MMzCVS4uXGOAGFvHoEWt--

--=-lCtu4vud9B4v51MEbkOu
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA/u15wakVQK4PsKXwRAmlMAJ9mjDL5NPZRJr0Nhw02CDkqrZYnwQCgrwc7
JRtoKi8QldAg01Oo5icufIE=
=sK5K
-----END PGP SIGNATURE-----

--=-lCtu4vud9B4v51MEbkOu--