Steve wrote:
> 
> Something I really miss from my VMS days is the sequential numbering
> of saved files, so that if I'm working on a scene file and save it
> it would save it as something like roundabout.pov;0000 and the next
> time I save it would write to roundabout.pov;0001 etc if I set my
> directory history to 20 that means that I'll always have the 20 most
> recent saves, a simple purge on the commandline will leave me with
> only the most recent files.  I'm sure that in bash it's possible to
> write something that will do the same job though the file naming
> will be slightly different to the way it is on VMS.
> 
> It'd be good if such a script could be called from pov's command line
> to let it usse the most recent for the current render you'd also need
> your editor to be able to understand this so maybe it's not going to
> be all that easy to implement.  I'll look into this myself but I don't
> promise to be able to come up with anything.

Why not use something like RCS (CVS would probably be overkill)? 
Depending on the editor you are using, you could probably configure it
to check in the file every time it saves, and you can easily delete the
archived versions if you decide you don't need them.  Using RCS won't
clutter up your directory with lots of copies of the same file either. 
I haven't used plain RCS recently, but here's some basic tips:

Make a directory called RCS (all in caps) in the directory where you
have your file.

The following command will see if the file filename.pov has changed at
all from the last copy saved, and if so, it will archive it.
ci -l -q -mauto -t-auto filename.pov

To view a list of all the copies which have been archived, use
rlog filename.pov

If you're not already familiar with RCS, take a look at the man pages
for rcs, ci, rlog, and co.  The commands I gave you above should be
enough to get you started though.

Ken

Post a reply to this message

On Thu, 29 Jun 2000 19:30:32 -0700, Ken Cecka wrote:
>
>If you're not already familiar with RCS, take a look at the man pages
>for rcs, ci, rlog, and co.  The commands I gave you above should be
>enough to get you started though.

Thanks Ken I'll look into this, didn't know it existed. 

-- 
Cheers
Steve              email mailto:ste### [at] zeroppsuklinuxnet

%HAV-A-NICEDAY Error not enough coffee  0 pps. 

web http://www.zeropps.uklinux.net/

or  http://start.at/zero-pps

  8:17am  up 8 days,  7:58,  2 users,  load average: 1.05, 1.13, 1.07

Post a reply to this message

Don't want to start a version control system war here, but I would like
to mention my experience about the subject.
  In the project we are working we used RCS at the very beginning and it
was a real pain in the a** to use it. Every directory have to have its own
RCS directory and trying to share the files with all the other members of
the project was really tedious and difficult. RCS also doesn't allow for more
than one person to modify the files at the same time. You can't have a
local copy of the project, which you can modify and then check in to the
version controlling system, but you have to edit them in a shared file system
(of course you can copy the files to yourself, but since RCS doesn't support
this, it's a pain). The locking of files is tedious because you have to
always remember to unlock the files that others may want to change.
  Then we changed to PRCS. What a heaven! All the directory structure could
be checked in to one single project file. You can have many sub-projects so
that you can work with intermediate versions that do not interfere with the
main version. More than one person can edit the same files at the same time
and PRCS can merge the files afterwards without problems (the problems only
arise if the persons edited the same lines of the files, which should be
avoided, but if they edit different lines, there's no problem at all).
Sharing the files with all the other members is very easy (every member
can have the latest version of all the subprojects with one single checkout).
Every member can have a local copy of the project (or any number of copies
if wished), only the main project file has to be shared. You don't have to
worry about locking and unlocking files; you just edit them and check them
in, that's it.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

I pretty much agree with your views on RCS.  I don't think I've ever run
into a group who uses RCS on its own for a large project.  I use
Rational's ClearCase at work which is wonderful.  I thought RCS might be
a good choice in this instance based on how Steve described what he
wanted to do.  If you're just working on a project on your own and are
just maintaining revisions of files, it might not be worth the trouble
of learning and setting up a full-blown cvs repository or something
similar.  But lots of options are always good.

Incidentally, what's PRCS?  I've only used ClearCase and CVS (RCS).  Is
it commercial?  CVS seems to be the system of choice at the moment for
opensource development, but there's a lot of functionality it's missing
that ClearCase has which makes life a lot easier.

Ken

Warp wrote:
> 
>   Don't want to start a version control system war here, but I would like
> to mention my experience about the subject.
>   In the project we are working we used RCS at the very beginning and it
> was a real pain in the a** to use it. Every directory have to have its own
> RCS directory and trying to share the files with all the other members of
> the project was really tedious and difficult. RCS also doesn't allow for more
> than one person to modify the files at the same time. You can't have a
> local copy of the project, which you can modify and then check in to the
> version controlling system, but you have to edit them in a shared file system
> (of course you can copy the files to yourself, but since RCS doesn't support
> this, it's a pain). The locking of files is tedious because you have to
> always remember to unlock the files that others may want to change.
>   Then we changed to PRCS. What a heaven! All the directory structure could
> be checked in to one single project file. You can have many sub-projects so
> that you can work with intermediate versions that do not interfere with the
> main version. More than one person can edit the same files at the same time
> and PRCS can merge the files afterwards without problems (the problems only
> arise if the persons edited the same lines of the files, which should be
> avoided, but if they edit different lines, there's no problem at all).
> Sharing the files with all the other members is very easy (every member
> can have the latest version of all the subprojects with one single checkout).
> Every member can have a local copy of the project (or any number of copies
> if wished), only the main project file has to be shared. You don't have to
> worry about locking and unlocking files; you just edit them and check them
> in, that's it.
> 
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Ken Cecka <cec### [at] alumniwashingtonedu> wrote:
: Incidentally, what's PRCS?

http://www.xcf.berkeley.edu/~jmacd/prcs.html

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Thanks to your earlier reply Ken I've got RCS up and running now,
it was a bit confusing at first as I've moved over to emacs at
the same time, and didn't understand how their bookmarks worked and
was opening other files and thinking that they were the same file and
wondering why emacs couldn't find the rcs entry etc etc.  But I've 
got it all sorted out now. 

-- 
Cheers
Steve              email mailto:ste### [at] zeroppsuklinuxnet

%HAV-A-NICEDAY Error not enough coffee  0 pps. 

web http://www.zeropps.uklinux.net/

or  http://start.at/zero-pps

 11:29pm  up 14 days, 23:10,  2 users,  load average: 1.36, 1.36, 1.25

Post a reply to this message