Woodchip created some ebuilds for peep, and now I'm retooling them. just starting a bug so I can keep track of my own work and centralize this dealy.
Well. I can see a few problems off the bat. I think we'd be better suited with a /etc/peep/ directory then just droping peep.conf into /etc. Looks like there are other files that can be used so no reason to clutter /etc up any more. Also, from the peep-sounds package, the actual sounds are getting installed but theme definitions are not. There are also some extra config files in that package that could go into /etc/peep. The peep-sounds package should only need to be modded to also install those files in the right spot. The core peep package looks like it will maybe need some adjustments to conf.d/peepd and some changes to the init script. Currently the init script doesn't seem to be parsing the conf.d script correctly. Doesn't really seem to be an issue with sound (as was originally thought). I think once we get all the files needed in the right place it should start up just fine. TODO: - create /etc/peep directory for the .conf files - make sure theme definitions are installed from peep-sounds - make sure extra configs are installed from peep-sounds - examine conf.d/peepd for possible changes - rewrite init.d/peepd to correctly parse conf.d/peepd - perhaps come up with a better default peep.conf
Looks like the extra configs and themes (collins.xml) should come from peep instead of peep-sounds. I've edited the peep ebuild to sed the peep.conf files intead of having to pull one in from ${FILESDIR}, install the extra config files, and also install the theme info into /etc/peep/themes. All config files have been moved into /etc/peep/ and the conf.d/peepd files has been updated accordingly. I'll rewrite the init script leter, as it's still not parsing conf.d/peepd correctly. I can start it manually by issueing `peepd --snd-device=/dev/dsp --config=/etc/peep/peep.conf --port=2000 -n`. It debugs it output and I can see it finds /dev/dsp ok, finds the theme ok and starts caching the sounds: [Fri Nov 8 18:01:30 2002] Loaded [/usr/share/peep/sounds/wetlands/states/water-02/water-02.01]: 530416 bytes. [Fri Nov 8 18:01:30 2002] Loaded [/usr/share/peep/sounds/wetlands/states/water-02/water-02.02]: 528908 bytes. [Fri Nov 8 18:01:30 2002] Loaded [/usr/share/peep/sounds/wetlands/states/water-02/water-02.03]: 528908 bytes. .. but then I get "Segmentation fault". ACK. I wasn't able to see the segfault message untill I used -n (Don't run in daemon mode). At least it's progress!
Created attachment 5490 [details] peep-0.5.0.ebuild Slightly edited peep ebuild. The ./configure step still isn't taking into acount ${myconf}, so alsa won't be used unless you edit manually.
Created attachment 5491 [details] peep-sounds-0.5.0.ebuild The peep-sounds ebuild. I changed this briefly, but I think it's back to it's original form now.
PEEP IS OFFICIALLY DRIVING ME CRAZY The server is running without segfaulting with no problems now. It parses it's own peep.conf fine, but I get this line near the end: Warning: Could not assemble a class identifier strings. a) Nice grammer b) I can't figure out what it means. It doesn't keep peep from running though. I think the website documentation confuses me more every time I read it. I've built "client" config sections, run the server, and then manually run the client programs. I can see in debug output that the server is receiving _something_ from the client, but I can never get the client to send the type of signal it was built to send! And forget sound. I haven't been able to get a single peep out of peep! And I don't know what this is supposed to mean: magic: [0xdeadbeef] ..but I'm sick of looking at it in debug messages. Just adding a helpfull update =)
This "bug" is now hosted at my dev site, http://cvs.gentoo.org/~mkeadle/, and is moved to unofficially, unsupported work for the moment.
Created attachment 28622 [details] peep-0.5.0_rc2.ebuild
Created attachment 28623 [details] peep-sounds-0.5.0.ebuild
Here are my latest peep ebuilds. I haven't had much time to setup a full proper config for my site, but it seems to be running just fine with test configs.
