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:

Proportional Font

LISTSERV Archives

LISTSERV Archives

STARDEV Home

STARDEV Home

STARDEV  May 2004

STARDEV May 2004

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: CVS discussion topics

From:

Norman Gray <[log in to unmask]>

Reply-To:

Starlink development <[log in to unmask]>

Date:

Mon, 31 May 2004 13:34:57 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (107 lines)

Tim,

On 2004 May 31, , at 01.03, Tim Jenness wrote:

> Pre-empting the discussion, I don't think it's an issue since most
> things
> can migrate from the current installation locations to a new
> "standardised" location without affecting other things. This is easy
> once
> everything works in CVS. [although we did agree that we should not be
> installing shared libraries into share]

True enough.  I think we should still have a brief chat about this, to
confirm it really is as straightforward as that, but no more than that.
  See below.

>> Anything else?  Is that a reasonable division?
>
> The install target needs to install versioning information somewhere so
> that the starversion command will continue to work. Currently
> starversion
> mainly looks in the datestamp files but there is no equivalent at the
> moment.

The manifest file which is installed by the `install-manifest' target
currently includes a <version> element which contains the version
declared in the configure.ac.  Is that sufficient?



DavidG: how's about this for the CVS part of the programmers' meeting
agenda?

1. Brief summary of status [Norman, 5m]

2. Arrangements for the CVS-week [Norman, 5m]

3. Outstanding CVS issues.  See message
<http://www.jiscmail.ac.uk/cgi-bin/webadmin?
A2=ind0404&L=stardev&T=0&F=&S=&P=245>.  Some of these issues (6: yes,
8: standing action?, 13: fixed?) have already been resolved, and the
thread after that contained some opinions.  Issue 4 probably doesn't
have to be decided now, since, as Tim points out, such a change can be
made centrally later.  Issue 10 (uninstaller) might be usefully
discussed here, but might be deemed purely technical, and thus
postponable to the CVS-week.  Any objections?  Anything else?  (see
also the `agenda' for the CVS-week).   [<10m, unless we do discover
problems that should be discussed here rather than in the CVS-week].

4. Packaging of components for separate distribution.  What should we
aim for?  When should we do it?  If the answer is `Debian + RPM
packages, during the CVS-week' then that's easy.  Or do we just do it
when we next get the chance?  There's probably no need for any
technical discussion, just the decision about what packaging goals
should be on the CVS-week agenda. [10m??]

[~ 30m to here]

5. Tagging and branching.  See the CvsTagging page for proposals, and
the thread starting with
<http://www.jiscmail.ac.uk/cgi-bin/webadmin?
A2=ind0404&L=stardev&T=0&F=&S=&P=15983> for some disagreements.  Is it
worth while aiming to resolve this at this meeting? [30-60m, probably]

[and this has to be scheduled in a morning session so that Tim can join
in from Hawai'i.]



...and this for the `agenda' for the CVS-week (partly from the `CVS
discussion topics' message of last week):

   1. CVS issues: 9: AST/Fortran link queries
   2. Uninstaller tool necessary (issue 10)?
   3. Testing (issues 11 & 12): should regression tests run before or
after installation?; do we need a separate installation test?
   4. Do we need separate `install' and `install-manifest' targets.
   5. Building documentation by default?  When?
   6. Distribution and packaging: technical issues not resolved at the
programmers' meeting.
   7. What `codeline ownership' features are desirable?
   8. [DLG's message:] Aim: get everything into CVS and set up new build
system ( checkout, configure, make) - working on various flavours of
Unix plus MacOS-X (and Cygwin/Windows if possible in the time
available). Note that the "essential" apps must build and work but
other low priority apps may fall by the wayside at this stage -
although even for these the code will be in the CVS repository.

That's turning into quite a lot of discussion at the CVS-week, rather
than the coding frenzy anticipated.  Is this inevitable, or has this
division of policy vs. coding got out of hand?  There seems to be a
danger that the CVS-week could turn into an extension of the
programmers' meeting, which is undesirable.

See you,

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