Thread: Noisy CVS updates
When I build from CVS I wind up with this in my CVS update email in the morning: ? GNUmakefile ? config.log ? config.status ? src/Makefile.global ? src/backend/postgres ? src/backend/bootstrap/bootstrap_tokens.h ? src/backend/catalog/postgres.bki ? src/backend/catalog/postgres.description ? src/backend/catalog/postgres.shdescription ? src/backend/parser/parse.h ? src/backend/snowball/snowball_create.sql ...etc. Would it be OK if I went in and added .cvsignore files to keep the noise level down? I guess I could have my daily script filter them out but there may be times when there really is an unexpected file and I want to follow up on it. -- D'Arcy J.M. Cain <darcy@druid.net> | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.
"D'Arcy J.M. Cain" <darcy@druid.net> writes:
> When I build from CVS I wind up with this in my CVS update email in the
> morning:
> ? GNUmakefile
> ? config.log
> ? config.status
> ? src/Makefile.global
> ? src/backend/postgres
> ? src/backend/bootstrap/bootstrap_tokens.h
> ? src/backend/catalog/postgres.bki
> ? src/backend/catalog/postgres.description
> ? src/backend/catalog/postgres.shdescription
> ? src/backend/parser/parse.h
> ? src/backend/snowball/snowball_create.sql
> ...etc. Would it be OK if I went in and added .cvsignore files to keep
> the noise level down?
Uh, no, at least not before you've explained why you get those messages
and others don't.
(Personally, I never do "cvs update" without "make distclean" first;
there are too many other ways to get screwed by updating a live build
tree.)
regards, tom lane
On Sun, 07 Sep 2008 03:39:39 -0400 Tom Lane <tgl@sss.pgh.pa.us> wrote: > "D'Arcy J.M. Cain" <darcy@druid.net> writes: > > ...etc. Would it be OK if I went in and added .cvsignore files to keep > > the noise level down? > > Uh, no, at least not before you've explained why you get those messages > and others don't. I didn't know that I am the only one. Am I? > (Personally, I never do "cvs update" without "make distclean" first; > there are too many other ways to get screwed by updating a live build > tree.) I assume that you are talking about conflicts. In fact, that's one of the main reasons for wanting a quiet update so that I can catch those right away when I am working on some files. I do an automatic update daily to keep current with the head. I don't do a "make distclean" first because I may be working on something and I want to keep the changes in the tree to try stuff and report patches against HEAD. -- D'Arcy J.M. Cain <darcy@druid.net> | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.
"D'Arcy J.M. Cain" <darcy@druid.net> writes:
> Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> (Personally, I never do "cvs update" without "make distclean" first;
>> there are too many other ways to get screwed by updating a live build
>> tree.)
> I assume that you are talking about conflicts. In fact, that's one of
> the main reasons for wanting a quiet update so that I can catch those
> right away when I am working on some files. I do an automatic update
> daily to keep current with the head. I don't do a "make distclean"
> first because I may be working on something and I want to keep the
> changes in the tree to try stuff and report patches against HEAD.
Huh? distclean does not remove any source-code changes, only derived
files.
regards, tom lane
On Sun, 2008-09-07 at 08:44 -0400, D'Arcy J.M. Cain wrote: > > Uh, no, at least not before you've explained why you get those > messages > > and others don't. > > I didn't know that I am the only one. Am I? You are not. I got more or less the same this morning while preparing my new packages. But as Tom stated, after running make distclean, everything worked fine. Regards, -- Devrim GÜNDÜZ, RHCE devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org
D'Arcy J.M. Cain wrote: > On Sun, 07 Sep 2008 03:39:39 -0400 > Tom Lane <tgl@sss.pgh.pa.us> wrote: > > "D'Arcy J.M. Cain" <darcy@druid.net> writes: > > > ...etc. Would it be OK if I went in and added .cvsignore files to keep > > > the noise level down? > > > > Uh, no, at least not before you've explained why you get those messages > > and others don't. > > I didn't know that I am the only one. Am I? Lots of other people do get them -- they are visible in the patches they send. Since I use a VPATH build, which puts all those files in a separate directory, I get (almost?) no noise even though I don't bother with "make distclean" most of the time. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
On Sun, 07 Sep 2008 10:39:25 -0400 Tom Lane <tgl@sss.pgh.pa.us> wrote: > > I assume that you are talking about conflicts. In fact, that's one of > > the main reasons for wanting a quiet update so that I can catch those > > right away when I am working on some files. I do an automatic update > > daily to keep current with the head. I don't do a "make distclean" > > first because I may be working on something and I want to keep the > > changes in the tree to try stuff and report patches against HEAD. > > Huh? distclean does not remove any source-code changes, only derived > files. Sorry, I was unclear. I meant that I might still be working on some source code changes and I didn't want to do a distclean every morning and then have to rebuild the tree in order to be able to work on my changes again. I use CVS in enough projects to understand how it works. -- D'Arcy J.M. Cain <darcy@druid.net> | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.
On Sep 5, 2008, at 9:06 AM, D'Arcy J.M. Cain wrote: > ...etc. Would it be OK if I went in and added .cvsignore files to > keep > the noise level down? I guess I could have my daily script filter > them > out but there may be times when there really is an unexpected file and > I want to follow up on it. +1. It might be possible to get screwed by not doing a distclean, but the build time savings seems worth it (first thing I do if I get a build error is make clean/distclean). -- Decibel!, aka Jim C. Nasby, Database Architect decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828
On Fri, Sep 12, 2008 at 07:27:55PM -0500, Decibel! wrote: > On Sep 5, 2008, at 9:06 AM, D'Arcy J.M. Cain wrote: >> ...etc. Would it be OK if I went in and added .cvsignore files to >> keep the noise level down? I guess I could have my daily script >> filter them out but there may be times when there really is an >> unexpected file and I want to follow up on it. > > +1. It might be possible to get screwed by not doing a distclean, > but the build time savings seems worth it (first thing I do if I get > a build error is make clean/distclean). maintainer-clean is even better as far as removing build errors, and I've never noticed any time difference between it and clean or distclean. Cheers, David. -- David Fetter <david@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate