release?

[Jeffrey R Lewis]

On Thursday, August 7, 2003, at 02:28 PM, Ross Paterson wrote:

> On Thu, Aug 07, 2003 at 01:52:05PM -0700, Jeffrey R Lewis wrote:
>> I think that the `Install' file at top-level should be up-to-date
>> before we release anything.  In particular, it should address the fact
>> that many people who might want to build hugs won't have fptools 
>> laying
>> about, so instructions for how to fetch an appropriate fptools
>> directory should be in there.
>
> The source bundle (as built by the top-level Makefile), will include a
> directory fptools in the hugs98 directory, containing the necessary 
> parts
> of hslibs and libraries.  This is what we distributed last November,
> and seems reasonable to do again -- the libraries have to match the
> version of Hugs shipped.  Once they've untarred that, it's exactly the
> short version in Install (or shorter).

OK, good plan.  We should lay down a tag in the libraries repo when 
hugs is released.

>
>> The recipie that I use is to go into the hugs directory (top-level),
>> and `checkout fpconfig', followed by `checkout libraries hslibs'.  Is
>> this all there is to it, or do I then have to go in and `make boot' or
>> somesuch in the fptools dir?
>
> That's all there is to it (no need to run anything inside fptools) -- 
> you
> don't even need fpconfig.  But those are the instructions for building
> from CVS, not from a source dist.
>

The current RPM.mk file checks out a much more specific list of 
directories under libraries and hslibs.  Is the list in RPM.mk 
up-to-date?  Is don't see anything in the commit history suggesting 
recently revisions related to which library directories to check out.

Also, the currently RPM.mk invokes autoconf, which chokes on 
configure.in under RH 7.2.  Is there any reason to run autoconf 
anymore, since configure is in the repo?

--Jeff