JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for STARDEV Archives


STARDEV Archives

STARDEV Archives


STARDEV@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

STARDEV Home

STARDEV Home

STARDEV  June 2004

STARDEV June 2004

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: HDS ssn27 and gen files.

From:

Norman Gray <[log in to unmask]>

Reply-To:

Starlink development <[log in to unmask]>

Date:

Wed, 16 Jun 2004 14:52:56 +0100

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (54 lines)

Tim and all,

On Tue, 15 Jun 2004, Tim Jenness wrote:

> All I'm really saying is that if we actually have the SCCS/CVS files or
> original .gen then I'd advocate starting from them rather than doing a
> fresh import from the tar ball and losing the history and/or original
> source.

I agree. If there are private SCCS/RCS/CVS files for a package that
hasn't been put into the repository yet, then yes, we should use these
rather than what's in /stardev/sources.

If there's something that has been put into the repository from the
tarballs, for which there are freshly-discovered SCCS/RCS/CVS files
(as is the case for NDF), then it would probably be good to merge that
history IF the files haven't diverged too far. I think it was Tim who
outlined a procedure for this earlier today. We should be terribly
disciplined about this, though, and if it looks like taking more than
a couple of hours, then just not do it; and certainly not do it during
the CVS-week.

Those things that we can't merge now will probably never get merged
(as Tim says). This probably isn't a big deal, since we know that
what's there at present works. What we'd have lost is the history, and
we can keep that by putting those discovered repositories in a separate
place in the CVS tree -- /code-archive, for example. If you have a RCS
repository in this category (possibly a SCCS repository converted to
RCS), then create a subdirectory /code-archive/blah on saturn, give it
the correct permissions (copied _carefully_ from other CVS directories),
and dump all the RCS files in. Those files' history can then be examined
in the usual CVS way, when necessary, without them having to be merged
anywhere (this was DLG's suggestion).

> Of course, the fact that we have .gen files for NDF and HDS now is a
> problem since, of course, those are already in CVS. It's not a priority to
> add those now, I'll put it on my todo list for when I've done GKS and AGI!
> At least .gen files can be added after the fact without direct
> manipulation of the repository.

It's probably pretty easy to switch back to .gen files during any
routine maintainance. And if there's no such maintainance, then
there's no need to do it.

How does that sound?

Norman


--
---------------------------------------------------------------------------
Norman Gray http://www.astro.gla.ac.uk/users/norman/
Physics and Astronomy, University of Glasgow, UK [log in to unmask]

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

December 2023
January 2023
December 2022
July 2022
June 2022
April 2022
March 2022
December 2021
October 2021
July 2021
April 2021
January 2021
October 2020
September 2020
August 2020
May 2020
November 2019
October 2019
July 2019
June 2019
February 2019
January 2019
December 2018
November 2018
August 2018
July 2018
May 2018
April 2018
March 2018
February 2018
December 2017
October 2017
August 2017
July 2017
May 2017
April 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
October 2015
September 2015
August 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
2004
April 2003
2003


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager