in reply to CVS and perl

Maybe I didn't understand your worries,
But using CVS with Perl code is just as using CVS with any other code
(At the office we use it for Perl, HTMl and PHP alltogether in the same repository (and even the same module soemetimes)...)

So the usual docs/tutorials about CVS would do fine.
(a good start could be this site)

And to answer your question :
How should I implement it with the existing environments ?

I'd need more informations : what do you want to implement what are YOUR problems, constraints...

"Only Bad Coders Badly Code In Perl" (OBC2IP)

Replies are listed 'Best First'.
Re: Re: CVS and perl
by indigo (Scribe) on Apr 13, 2001 at 03:03 UTC
    A little nit...

    Using CVS with Perl code is not just as using CVS with any other code. At least not when looking at the whole configuration management picture. Most CM models assume C-style code compilation, so a lot of general documentation on version control tools are going to assume you need to muck about with source and object code and libs and executables. The Perl way is simpler, of course, but I have seen CM's get tripped up trying to apply the traditional logic without making adjustments. Since the poster is messing with both Perl and C, he should probably be aware of this.
[reply]
      However note that a Perl project which is using something like Template Toolkit, then some thinking needs to go on about combining checkins with builds...

      OK, not as much since the build time is likely to be reasonably quick, but it does arise.

[reply]
Re: Re: CVS and perl
by toadi (Chaplain) on Apr 12, 2001 at 16:48 UTC
    For the moment we have a server and a db for alpha development. Everyone can develop on it and everyone can acces anyones files...

    Then we got the production server with db.

    For the moment we are setting up a beta test-environment.
    My question is where does CVS fit in? For the moment I edit on the alpha server. When it works I drop it in production(soon step in between:beta). Do I need to keep editing on the alpha server and push it in the cvs?
    Don't really understand how I can implement it. Got the rough idea on how and what it does... But with actual using it, I have no clue...


    --
    My opinions may have changed,
    but not the fact that I am right

[reply]

      For the moment we have a server and a db for alpha development.
      Everyone can develop on it and everyone can acces anyones files...
      Then we got the production server with db.

      As you seem to NOT have strong right-checking policy, here is my suggestion :

      Put the CVS server on the test server, use an 'autoexport feature' (triggered by the loginfo file)
      to maintain an exact working copy of your repository on your test server.
      I'd suggest to make modules based on directories. (to benefit of the 'autoexport')

      When everything is ok, all you'll have to do, is to 'scp' (you read well ! not 'ftp' !) the files to the prod server...

      "Only Bad Coders Badly Code In Perl" (OBC2IP)
[reply]

In Section Meditations