[3020] in SIPB bug reports
gnuserv not installed properly in sipbsrc
daemon@ATHENA.MIT.EDU (Calvin Clark)
Wed Jul 8 20:28:29 1992
Date: Wed, 8 Jul 92 20:27:46 EDT
From: Calvin Clark <ckclark@MIT.EDU>
To: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
Cc: bug-sipb@Athena.MIT.EDU
Reply-To: ckclark@MIT.EDU
I should think that sipbsrc would get pretty big if we decided on that
goal. That's not to say that it isn't a reasonable goal, because there
are clear benefits. I apologize for my ignorance if it was decided long
ago to keep populated build trees for every program. In the past, I
have had a tendency to do a "make clean" in any build tree for a program
which does not often require debugging, just for the sake of saving disk
space. It seems that from looking at the number of build trees under
rsaix in comparison to those under vax that this precedent, if it ever
existed, has not exactly been followed of late.
I'm going to take this opportunity to bring up an issue that's probably
been brought up a zillion times before. I'll bring it up in this forum,
which is probably the wrong place for it. Then again, maybe it's not.
Maybe followups should go to Whither-SIPB.
There are many things that would be nice in the sipb locker. It would
be nice if the whole thing could be built from a top-level
Imakefile/Makefile, like the Athena source tree. It would be nice if
everyone updated FILES.look when installing new programs, etc. Some
things are easy, and it's just a matter of making sure everyone knows
what to do. Other things (like a top level full build) take a lot of
work to do properly.
I know that you have given some degree of thought to this in the past,
and you have obviously done a lot of work to improve the quality of
maintainance in sipbsrc.
I don't see any POLICY file in the sipbsrc locker. Maybe there should
be one. I don't think you should write it. I don't think I should
write it. I think it should be written by those who are likely to be
maintaining the sipb locker next year, the year after that, and the year
after that. Maybe some of us fogies can give some advice, but it better
be short and to the point, otherwise no one's going to remember all of
it (which is one reason why it should be written down.)
Some new prospectives will be membered in September, and hopefully more
people will wish to join if we don't scare them away too soon. The way
I see it, we have a couple of months to decide what to tell them.
What's it going to be?
-Calvin
