firefox032697
asked on
Is RCS / CVS Y2K compliant?
My underlying OS (SVR4) is Y2K compliant but I was wondering whether RCS and CVS was capable of storing and manipulating dates beyond 1999?
Has anyone actually tested this?
Iis there anything like a site that could provide an "official" answer to this question (eg. support@gnu.com)?:
Has anyone actually tested this?
Iis there anything like a site that could provide an "official" answer to this question (eg. support@gnu.com)?:
In general most unix applications that have been rewritten several times (RCS certainly has), will use the unix time C library. This is a 32 bit counter from 1/1/1970 in seconds. So it will wrap round in 2038.
However, anything compiled using very recent libraries (ie last year or so), will probably be using a 64 bit counter. This will expire in about 500,000,000,000 - the Earth is set to be swalled up by the Sun in about 20,000,000. So no need to worry there!
I know this doesn't answer the question, but it's interesting all the same...
However, anything compiled using very recent libraries (ie last year or so), will probably be using a 64 bit counter. This will expire in about 500,000,000,000 - the Earth is set to be swalled up by the Sun in about 20,000,000. So no need to worry there!
I know this doesn't answer the question, but it's interesting all the same...
RCS and SCCS store dates in the form yy/mm/dd, so they are not Y2k complient.
AFAIK, SCCS uses 1969 as base (not 1970) and therefore is y2k complient 'till 2068.
AFAIK, SCCS uses 1969 as base (not 1970) and therefore is y2k complient 'till 2068.
I just checked GNU's implementation of RCS and they explicitely mention
that:
'Y' contains just the last two digits of the year for years from 1900 through
1999, and all the digits of years thereafter. Dates use the Gregorian calendar;
times use UTC.
This makes me feel quite confident the (at least GNU's) RCS is Y2K 'safe' ...
kind regards,
Jos aka jos@and.nl
that:
'Y' contains just the last two digits of the year for years from 1900 through
1999, and all the digits of years thereafter. Dates use the Gregorian calendar;
times use UTC.
This makes me feel quite confident the (at least GNU's) RCS is Y2K 'safe' ...
kind regards,
Jos aka jos@and.nl
jos, it couldn't be Y2K safe if it just uses 2 digits per year.
Example:
have a file with deltas made
01-jan-1999, 31-dec-1999,
01-jan-2000, 01-jan-2099, 02-jan-2099, 31-dec-2099
then use:
co -d"1999-01-01" file
co -d"2099-01-01" file
to get it back.
I never tested this, but I expect that you get deltas from 01-jan-1999 and newer for both co commands.
Example:
have a file with deltas made
01-jan-1999, 31-dec-1999,
01-jan-2000, 01-jan-2099, 02-jan-2099, 31-dec-2099
then use:
co -d"1999-01-01" file
co -d"2099-01-01" file
to get it back.
I never tested this, but I expect that you get deltas from 01-jan-1999 and newer for both co commands.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://www.cyclic.com/cyclic-pages/sccs.html
http://www.cyclic.com/cyclic-pages/rcs.html
http://www.cyclic.com/cyclic-pages/CVS-sheet.html
http://www.myth.co.uk/~jay/cssc/