YAPC::NA uncovers some problems in Strawberry

Alias on 2008-06-23T21:09:25

The great thing about mixing with more people face to face is that you discover things that most people won't necesarily be bothered about enough to send you email or a bug report.

During YAPC::NA, a couple of interesting problems were described to me that might help explain some of the discrepancies I've been seeing in Strawberry download numbers, compared to cpan.strawberryperl.com download numbers.

Firstly, a few people mentioned that there's no way to get more information about Strawberry for people that care about these things. What is it made from, what things does it include, what comes bundled, etc etc. The website is just too lacking in information.

While I don't have time to fix this right away in a heavy way, I've started by adding a link to win32.perl.org on the front page. I'll give this a few weeks and see how things turn out, then after OSCON (and after the Strawberry Portable release) I'll see if there's anything more that can be done.

Secondly, after helping a friend of Schwern's to install Strawberry, I realised I've made something of a silly assumption.

The friend in question was in the typical position of being a Unix Sysadmin/DBA but had a Windows laptop due to corporate policy. But after installing Strawberry Perl, she hadn't even considered that she should launch the command line, in fact she didn't even know how, because she'd never had to before.

This exposes something of a problem, because although Strawberry Perl is intended for experienced Unix people, the assumption that such people will connect "runs like on Unix" to "use the Windows command line" is wrong.

Further, this also exposes the problem that people that SHOULD be using Chocolate rather than Strawberry currently don't actually have Chocolate at all. But word of mouth continues to push them towards Strawberry.

So I think I need to take a look at providing a bit more information to help people after the installation is complete.

I'm wondering if a simple screencast would be enough, your thoughts?


Screencast

chromatic on 2008-06-23T21:57:23

I'm wondering if a simple screencast would be enough, your thoughts?

Perl.com and O'Reilly News would be very interested in hosting or promoting such a thing.

Sample setups

dagolden on 2008-06-23T23:23:10

If we can assume for the time being that someone installing Strawberry is able to help with getting things set up, then maybe hosting some real-world sample setups would be useful, even if it means some work on their part.

For example, I have a shortcut that opens a command window in my projects directory. That's where I "start" work.

The I have a bunch of helper programs that provide my coding toolbox. For example, vim/gvim. And the great unxutils project at sf.net (but with any tar, zip, etc. since I've found them to be broken). Plus the SVK binary. (Git binary too, but that's pretty rocky on the command line still.)

The other very good thing to have would be a walk through of installing, say, the OpenSSL library and then Crypt::SSLeay. And or one of the libraries that is best installed into the c:\strawberry\c\lib directory. (It's all kind of there on win32.perl.org, but it's not quite definitive.)

List of what's included should be fairly easy to generate from Module::Corelist and then the add-ons in Perl::Dist::Strawberry.

-- dagolden

P.S. not volunteering yet, just brainstorming. I'm still in a tuit deficit for a while.

screencast++

rjbs on 2008-06-24T01:24:07

I think a screencast showing how one might use the now-installed perl sounds like a good idea to start with. A screencast is worth a million words.

Strawberry icon

grink on 2008-06-24T05:28:20

How about a nice, juicy strawberry icon that will launch the Windows command line. Have the terminal start out by echoing out some usage tips.

Now people will have an icon they can click on.

Re:Strawberry icon

dagolden on 2008-06-25T14:19:30

+1