Re: help for module name?
On 07/05/27 21:27 +0200, A. Pagaltzis wrote: well, i don't like the way to prereq sthg in pococm that i won't really use - that is, the whole non-poe logic of audio::mpd. What whole non-POE logic? All the logic I can find is the as_string method. Are we talking about the same modules? i was talking of adding in this helper dist the modules stats, status and time (always in audio::mpd::) which are also just structs and are shared between the poe and non-poe implementation. thus, the dist audio::mpd::items would not be enough - unless i also release separately audio::mpd::stats and... which is a bit silly imo. therefore: - audio::mpdhelper? - audio::mpdcommon? regards, jérôme -- [EMAIL PROTECTED]
Re: help for module name?
Le lundi 28 mai 2007 à 08:47, Jerome Quelin écrivait: thus, the dist audio::mpd::items would not be enough - unless i also release separately audio::mpd::stats and... which is a bit silly imo. therefore: - audio::mpdhelper? - audio::mpdcommon? Maybe Audio::MPD::Common, so that everythings stays in the namespace you're using? -- Philippe BooK Bruhat In war, the only winners are those who sell the weapons. (Moral from Groo #3 (Image))
Re: US mirror of search.cpan *broken*
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28 May 2007, at 00:30, Jonathan Rockway wrote: The bizrate search.cpan is broken. The most recent module (judging by the recent tab) is from 5 days ago, 23 May. I'm told that the UK mirror (digitalcraftsmen) is running fine. Ah. That explains why I can see http://search.cpan.org/dist/Captcha-reCAPTCHA but folks in the US can't. So yes I can confirm that the digitalcraftsmen mirror is fine. - -- Andy Armstrong, hexten.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFGWrH6woknRJZQnCERAt97AJ9v+g4BUiWgjKHVWrBBzR0K3PNmqgCgm4dw +eIpUtBgMuTGuUlFeU2ZNRk= =6JXL -END PGP SIGNATURE-
Re: help for module name?
Le lundi 28 mai 2007 à 13:11, Jerome Quelin écrivait: On 07/05/28 12:31 +0200, Philippe 'Book' Bruhat wrote: thus, the dist audio::mpd::items would not be enough - unless i also release separately audio::mpd::stats and... which is a bit silly imo. therefore: - audio::mpdhelper? - audio::mpdcommon? Maybe Audio::MPD::Common, so that everythings stays in the namespace you're using? but it's to be used also in the namespace poe::component::client::mpd == therefore, why take one rather than the other? Because it's not POE specific, so it should live in the POE namespace. -- Philippe BooK Bruhat For every winner, there must be one or more losers. (Moral to the Sage story in Groo #111 (Epic))
