Re: Bug: Current CVS in Playlist.pm
Amos Hayes <[email protected]>
| Newsgroups | gmane.music.equipment.slimp3.dev |
|---|---|
| Message-ID | <[email protected]> |
On Tue, 23 Oct 2001, Mark C . Langston wrote: > Out of curiosity, is there a better way to approach this? Otherwise, > we're going to end up with a hefty chunk of the real CPAN as part of > the distribution...not an ideal situation. > The downside is that I don't have a better solution to suggest, so > this boils down to a pointless mini-rant. ;) It's a pain for sure. Ease of setup for the end user is probably the the prime benefit (especially as far the folks selling these things are concerned) but it's also very important to lock in a particular version of these modules so that problems aren't introduced my module changes. This way a slimp3 developer will need a good reason to upgrade a module and will presumably test the integration before checking it in. It would be good for someone (probably Sean on a dedicated system... his business :) ) to be our plain vanilla perl install tester. Certainly before any file release, we'll need to make sure that we've included everything that we depend on. In the meantime, it looks like Mike will sound the alarm. It looks like the rest of us have added many CPAN modules to our site-perl already and won't easily catch these things. Hmmm... unless we can explicitly remove site-perl from @INC in the slimp3 server? -- Amos Hayes [email protected] ------------------------ Yahoo! Groups Sponsor ---------------------~--> Pinpoint the right security solution for your company- Learn how to add 128- bit encryption and to authenticate your web site with VeriSign's FREE guide! http://us.click.yahoo.com/yQix2C/33_CAA/yigFAA/rIp0lB/TM ---------------------------------------------------------------------~-> To unsubscribe from this group, send an email to: [email protected] Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/