[1809] in SIPB bug reports
freeze, patch01
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Wed Apr 3 01:52:10 1991
Date: Wed, 3 Apr 91 01:51:36 -0500
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: eichin@ATHENA.MIT.EDU
Cc: bug-sipb@ATHENA.MIT.EDU
In-Reply-To: "Mark W. Eichin"'s message of Sat, 30 Mar 91 10:04:31 -0500 <9103301504.AA20222@bill-the-cat.MIT.EDU>
Date: Sat, 30 Mar 91 10:04:31 -0500
From: "Mark W. Eichin" <eichin@ATHENA.MIT.EDU>
What's the right way to do an install?
"detach sipb; attach -t afs -e /afs/.athena/contrib/sipb; make
install".
And why doesn't the Imake
generated makefile have a "make links" target? (This patchlevel added
a patchlevel.h file, as well as my statist.man. Consider this a bug
report on the Imake config files...)
Because I use synctree to generate all of the symlink forests. It's
much faster and easier to use than a "make links" rule, and probably
more reliably.
The freeze source dir already has a .rconf file. Therefore, you can
use do "attach synctree; /mit/synctree/synctree -s
/afs/sipb/project/sipbsrc/src/freeze -d
/afs/sipb/project/sipbsrc/@sys/freeze".
Note that the Imake config files we're using are the standard X
configs. If you think they should support "make links" by default
(something with which I disagree), then you can report the bug to them
directly.
Most of this should be in
/mit/sipbsrc/src/MAKEFILE_RULES, along with the instructions already
present on how to create a new project.
Probably, but that file hasn't been updated in a long time, and it
talks about Makefile's not Imakefile's, which support most of what's
listed there automatically. What you're essentially asking me to do
is document how the X Imakefiles work. No thanks. I have little
enough time for maintaining the sources that I maintain.
Little things which should be "written down":
Imakefile use - ComplexProgramTarget vs. ComplexProgramTarget_1
This is another case of asking me to document how the X Imakefiles
work. UTFL. That's how I learned.
remember to add the directory to src/Makefile (freeze wasn't...)
Yup, I forgot this. This would probably turn up the next tim I tried
to build and install the whole locker from scratch. There are
probably other dirctories missing as well.
attach what? where? and do what make? for each architecture...
See above.
what AFS commands are needed (or who needs to be tweaked? or at
least, how long do we wait for it to happen automatically?) for this to
appear in the SIPB locker?
It happens automatically some time late at night.
Many of these things have changed since I last did serious
maintenance of the SIPB locker; while jik is doing a great job of it, he
occasionally leaves for Ohio... and this should really all be documented (so
the jik script can display it? :-)
You're right. If you have time to learn and document it, go right
ahead. But I don't have time right now to write it all down, although
I'm quite happy to explain it to anyone who asks. That doesn't take
as long as writing a detailed, precise explanation, especially since
not many people ask. :-)
jik
