[Andrew Bardsley <address@hidden>] gEDA: Espresso

[Thien-Thi Nguyen]

(define-module (eda INIT)
  :use-module (eda espresso)
  :use-module (eda gschem-control) ...)

etc.  who would like to write this?  where would it fit wrt to
$w/modules/module-layout.text ?  how to use writing experience in design
of "versioning scheme modules"?  where are the bridges to xfig et al?
[your question here.]  maintainer wannabes w/ desire to curry favor
prepare for the fastest finger question: put these file access tuples in
chronological order for a normal `new-change' cvs repo transaction:

        parent/ChangeLog -- cvs commit
        parent/ChangeLog -- edit
        $w/tasks/TODO    -- cvs checkout
        parent/file      -- edit
        $w/tasks/TODO    -- cvs commit
        parent/          -- create
        $w/tasks/TODO    -- edit
        parent/ChangeLog -- cvs checkout
        parent/file      -- cvs commit

bonus points for providing correct modifications to also indicate a
`file-change' flow.  "correct" may include threading.  bonus for
handling trees where ChangeLog may be above file.  bonus for writing
module (scripts cvs-control).  bonus for writing elisp glue.  double
bonus for using guile to execute this elisp.  bonus for a patch to
trigger everything from "make check".  [your bonuses here.]

(also, some claimed TODO tasks have been claimed for over a month.  who
would like to write the watchdog cron job?)

thi


------- Start of forwarded message -------
Date: Mon, 22 Apr 2002 14:43:35 +0100 (BST)
From: Andrew Bardsley <address@hidden>
To: <address@hidden>
Subject: gEDA: Espresso
Message-ID: <address@hidden>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: address@hidden


I've found the Berkeley logic minimiser Espresso an absolute pain to build 
in the past. So I've cleaned the code up a bit and applied a small amount 
of automake/autoconf.

The result is the package: espresso-ab-1.0.tar.gz

ftp://ftp.cs.man.ac.uk/pub/amulet/balsa/other-software/espresso-ab-1.0.tar.gz

Which should be easier to build on modern systems. I've ANSIfied the code 
a little and removed the half-a-libc set of memxxxx/strxxxx/... 
replacement files which espresso is supplied with.

There's an original espresso tar.Z file in the same dir. and the espresso
copyright (espresso.copyright).

Enjoy

- Andrew
    _______________
___/Andrew Bardsley\____________________________________________
University of Manchester Dept. of Computer Science  AMULET Group
Research Associate bardsleyATcs.man.ac.uk  Tel: +44 161 275 6844
Snail: Room IT302, Man. Uni., Oxford Rd, Manchester, M13 9PL, UK
------- End of forwarded message -------