🚀 go-pugleaf

(This posting is emailed to bug-glibc@prep.ai.mit.edu as well)

Firstly:
Hey!  The glibc-1.05 files on prep.ai.mit.edu keep changing size!!

Near 10/2 the glibc-1.05-crypt.tar.Z got replaced, and now I see that
glibc-1.05.tar.Z was replaced on 10/6.  
I don't know what's been changed, but the files are different sizes than
the originals.

Please, when you decide to release a version -- Freeze it !!  

Do not put a patched version in a file of the same name as the original,
because many of the sites that try to do a service and mirror prep will
be extremely confused and outdated.

If you want to make minor changes, jump a rev level or wait until the
next release, or call it 1.05-plN


Secondly:
Several days ago someone claimed you didn't have a prayer of building
glibc 1.05 without a make-3.62 patchlevel d or something like that, that
was only on alpha.  Since at the time there was a make-3.62 on prep,
I read him as saying the make-3.62 on prep was unable to make the glibc.

I thought: this guy's mistaken -- I've talked with a glibc maintainer
about unsuccessful builds and my problems didn't trigger any suspicions
of the make sw.
But on the other hand, I never did succeed in making glibc and this
guy's claim wasn't refuted.  Could it be??
(My probs were in zic'ing Africa during make, if I remember right -- I'm
on SunOS 4.1.1 using gcc-2.2.2 and make-3.62 (from prep!))


Thirdly:
Regarding version stamping -- obviously a lot of GNU ware developers 
don't use SCCS, but I assume they use something (RCS?).  So is there a
simple command, like SCCS's "what", that will tell me the version stamps
of sources (and executables with a version stamp string)?

Regards,
ruck
-- 
John R. Ruckstuhl, Jr.                  ruck@alpha.ee.ufl.edu
Dept of Electrical Engineering          ruck@cis.ufl.edu, uflorida!ruck
University of Florida                   ruck%sphere@cis.ufl.edu, sphere!ruck