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.
  • This is very sad news, Sky. Maybe the problem is just that it's still not in a final release form. Let us hope so.

    In the meantime, I got an email this week from somone at Perforce saying that they give out free licenses for open-source projects. I'll forward the mail to you.

    --David

    • Re:P4 (Score:3, Informative)

      [Perforce] give out free licenses for open-source projects

      perl5 already uses Perforce as its version control repository. Ignoring the issues about open/closed source software, I seem to remember at least 3 practical problems with it:

      • It does checkouts over ssh, which means that the user has to maintain a ssh tunnel to the repository machine, and the repository machine owner has to maintain the ssh authorized keys file
      • It can't do anonymous read only access
      • Every year the licence key has to be renewed. Thi
      • Each ssh tunnel counts as a user, so I can't have 3 different machines tunneling into the repository simulatenously on 1 licence - I have to drop the connection before starting up the new one.

        Strange. Perforce licenses are normally counted per named user. A named user can have an unlimited number of simultaneous connections (read: client workspaces) to the repository. Of course, the free licenses for open-source projects might differ in this respect from the normal payed-for licenses, which are the ones th

  • Try arch (Score:3, Informative)

    by Matts (1087) on 2003.07.31 12:28 (#22632) Journal
    Really try arch (or tla or ArX). It's quite a bit different to using CVS (and thus I assume SVN), but it seems to work.

    Check outs can be slow as they start at a base revision and then work through applying the patchsets, but you can optimise by providing checkpoints along the way. It's all in the manual.

    I know people don't want to try arch because of Tom Lord. That's a shame, as it'd be like not trying qmail because of djb.
    • it is also a bunch of awk scripts
      --
      sky
    • Check outs can be slow as they start at a base revision and then work through applying the patchsets,

      Sounds a bit like SCCS.

      I know people don't want to try arch because of Tom Lord. That's a shame, as it'd be like not trying qmail because of djb.

      I don't know Tom Lord, but I'm fairly sure I've heard of people who won't try qmail (or djbdns, or whatever) because of djb.
      --

      -- 
      Esli epei eto cumprenan, shris soa Sfaha.
      Aettot ibrec epesecoth, spakhea scrifeteis.