[ date ] 2004/02/22 | Sunday | 04:07 PM
[ author ] Tels <[EMAIL PROTECTED]>
> Moin,
> having a look at the newly checked out code from sdl-perl, I notice that the
> BUGS file is about 700 K and contains a lot of garbage. Is this a problem
> on my end, or a problem in the repository?
I got a huge BUGS file, too.
I asked `file` to analyze it for me, and it said that it was gzipped
data. Then I gunzipped it, and it when I looked at it in a text editor,
it looked like a tar file, so I zipped it up again and renamed it
BUGS.tar.gz. When I looked at the file listing, it looked to me like a
partial archive of sdl-perl.
I impulsively untarred it, too, and it overwrote a bunch of files in
place (doh!).
Recommended action:
svn rm BUGS
I've been itching for a good chance to use subversion for a while, and
sdl-perl finally gave me a good excuse. I'm looking at the commands
that `svn help` displays, and I'm stoked. It's like CVS but better!
PS: I like the way chromatic did the SDL::Config checks in t/ttfontpm.t.
I put way too much in the BEGIN block on the patch that I submitted.
My excuse is that I work on a project that has a module that
requires certain things to happen in a BEGIN block (or things go
horribly wrong), so I'm a little BEGIN-happy.
PPS:
A general Perl testing question -- Does anybody know how to run
individual tests in the t/ directory? There have been times when
I'm working on modules where I just want to run one set of tests
instead of the whole test suite, but I don't know of any standard
mechanism that allows that. If anyone could clue me in, I'd really
appreciate it.
