Norman
after a cvs update, what is the sequence of commands to build everything
again. I've had problems doing that.
...David
-----Original Message-----
From: Starlink development
To: [log in to unmask]
Sent: 11/03/2004 15:49
Subject: [CVS] notifications
Dear all,
Mark reported a problem with the install-manifest target in pcs. This
is fixed, so you'll get updates to Makefile.{am,in} next time you
update libraries/pcs, however you'll also get updates to automake next
time you update that. I have tinkered with automake a number of times
in the last few weeks, but haven't bothered to announce the changes.
Since folk are currently still experimenting with whole-tree builds,
you'll tend to update or checkout buildsupport and thirdparty/fsf fairly
regularly, but this will become less frequent fairly soon, I expect.
I suggest that commits to ., buildsupport and thirdparty/fsf be mailed
to the stardev list via the CVS loginfo mechanism, as a warning that
these need to be updated and possibly rebuilt. Does that sound
reasonable, or would folk want a finer-grained mechanism, where it
only went to certain individuals?
Just by the way, the <developers> element in the component.xml file is
intended to support something similar, eventually. It should be easy to
extract email addresses for all those <developers> children in component
X which have a mailupdates="yes" (say) attribute, and have those as the
recipients for that component's loginfo messages.
Now! On to primdat....
Norman
--
------------------------------------------------------------------------
---
Norman Gray
http://www.astro.gla.ac.uk/users/norman/
Physics and Astronomy, University of Glasgow, UK
[log in to unmask]
|