Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Here's my attempt.

    Checked out revision 24297.
    parrot $ cd parrot
    parrot $ perl Configure.pl
    Base class package "Parrot::Configure::Compiler" is empty.
        (Perhaps you need to 'use' the module which defines that package first.)
    at lib/Parrot/Configure.pm line 44
    BEGIN failed--compilation aborted at lib/Parrot/Configure.pm line 44.
    Compilation failed in require at Configure.pl line 299.
    BEGIN failed--compilation aborted at Configure.pl line 299.
    parrot $ find . -name Compiler.pm
    ./languages/jako/lib/Jako/

    • It looks like one of the configuration system branch merges missed a file, so until Jim can fix it, try r24278; that's one I know is good.

      • This kind of remark is exactly the sort of reason why it is a good idea to ditch Subversion and move to a decent Source Control Management system. Producing a stable branch with Subversion is not common practice, because the tools make it hard and do not support every stage of the process.
        • I agree that Subversion's merging support has its flaws. However, there's no point in even thinking about considering the possibility of allowing the idea of having this conversation cross your mind until there's a working and native Git port for Win32. We have a couple of active Win32 developers, and anyone who willingly develops on that platform I will not chase away.

          • Won’t be this way for very much longer [google.com], considering the speed at which git’s been moving since inception.

          • As the unofficial native Win32 tool purist, I've recently withdrawn my objects to git.

            The new native git installer does almost everything right, it's just still got a lot of bugs to be cleaned (but no show stoppers).

            Moving to git should only be a matter of when now, not if.
        • What would you recommend as a "decent" SCM system?

          • Git, of course. :-)

          • I have in the past recommended several [oreillynet.com].

            However I think of those three git is the right one to standardize on for a repository format, as it's the most efficient for that and all the other tools can work well with it. It's also the simplest to understand, with a model sporting only four basic types - files, directories, commits and tags. The representation of this in Perl6 is delightfully small; I used it as a model example for my 2006 Moose Talk [utsl.gen.nz] at YAPC::Eu.