Comments for wxCPANPLUS http://wxcpan.wordpress.com A Wx GUI fro CPANPLUS Mon, 12 Jan 2009 08:19:32 +0000 http://wordpress.com/ hourly 1 Comment on I’m still here! by Adam Kennedy http://wxcpan.wordpress.com/2009/01/07/im-still-here/#comment-50 Adam Kennedy Mon, 12 Jan 2009 08:19:32 +0000 http://wxcpan.wordpress.com/?p=47#comment-50 You might want to come hang out on irc.perl.org #padre. We're accumulating quite the cabal of cross platform Wx.pm people here. And we'd love to integrate wxCPANPLUS into the IDE :) You might want to come hang out on irc.perl.org #padre. We’re accumulating quite the cabal of cross platform Wx.pm people here.

And we’d love to integrate wxCPANPLUS into the IDE :)

]]> Comment on Week[11]: Finale, Future and Farewell! by Kamy Lamm http://wxcpan.wordpress.com/2008/08/19/week11-finale-future-and-farewell/#comment-49 Kamy Lamm Fri, 22 Aug 2008 08:56:57 +0000 http://wxcpan.wordpress.com/?p=44#comment-49 You have a nice blog with good and bad experience. It proves that every technology have its own advantage and disadvantage. You have a nice blog with good and bad experience. It proves that every technology have its own advantage and disadvantage.

]]> Comment on Week[6] Report: Wizards roll 1d12 for saving throw! by Steffen Mueller http://wxcpan.wordpress.com/2008/07/14/week6-report-wizards-roll-1d12-for-saving-throw/#comment-23 Steffen Mueller Mon, 14 Jul 2008 18:26:42 +0000 http://wxcpan.wordpress.com/?p=29#comment-23 Hi Sam, glad to hear you're still making good progress. I have approved your namespace registration via PAUSE, so you can upload a first implementation any time you'd like. If you just assign a version with an underscore, a release will be flagged as a developer release. It will not be indexed by PAUSE and therefore not be installable via "cpan CPANPLUS::Shell::Wx" or similar. It will be installable by full path however, and the CPAN testers will get a go, too. So please don't hesitate to upload developer releases which aren't quite the most round experience. Just go ahead and experiment! Best regards, Steffen Hi Sam,

glad to hear you’re still making good progress. I have approved your namespace registration via PAUSE, so you can upload a first implementation any time you’d like.

If you just assign a version with an underscore, a release will be flagged as a developer release. It will not be indexed by PAUSE and therefore not be installable via “cpan CPANPLUS::Shell::Wx” or similar. It will be installable by full path however, and the CPAN testers will get a go, too. So please don’t hesitate to upload developer releases which aren’t quite the most round experience. Just go ahead and experiment!

Best regards,
Steffen

]]> Comment on Week[0] = Ahead of Schedule; SVN Problems Ensue by Chris Dolan http://wxcpan.wordpress.com/2008/06/01/week0-ahead-of-schedule-svn-problems-ensue/#comment-4 Chris Dolan Mon, 02 Jun 2008 04:02:55 +0000 http://wxcpan.wordpress.com/?p=10#comment-4 This sounds like a case-sensitivity issue. When I see error messages like that, it's usually because the SVN server has a case-sensitive filesystem (e.g. Linux/BSD) while the client is case-insensitive (Mac/Win), and someone earlier committed two files which differ only in case from a case-sensitive client. If I'm right, one solution is to use a case-sensitive client to "svn rm" one (or both) of the conflicting files and then "svn update" the case-insensitive clients. A long-term solution is to add a pre-commit trigger that checks for invalid filenames. A web search will surely turn up such a trigger script for case-sensitivity issues. This sounds like a case-sensitivity issue. When I see error messages like that, it’s usually because the SVN server has a case-sensitive filesystem (e.g. Linux/BSD) while the client is case-insensitive (Mac/Win), and someone earlier committed two files which differ only in case from a case-sensitive client.

If I’m right, one solution is to use a case-sensitive client to “svn rm” one (or both) of the conflicting files and then “svn update” the case-insensitive clients.

A long-term solution is to add a pre-commit trigger that checks for invalid filenames. A web search will surely turn up such a trigger script for case-sensitivity issues.

]]>