Re: packaging beepcore-c

William J. Mills wrote:
 > The question of Debian packaging I think is that it would be
 > welcome.  The guy who did the last major revision of the build
 > structure is Bruce Michener, and I am not sure what his status
 > is currenlt for spending time ome BEEP, but he'd be the best
 > resource for questions of the current structure of how the
 > build happen.

I'm around but haven't had a lot of time for some months.  I'm happy to 
see someone interested in doing this work.

If I could squeeze a couple of other questions in:

    How is a beepcore-Python going?
    What happened with the threading changes to beepcore-C?

 > As to include files.  There was a while ago, and it may still be
 > an open item, a question of some refactoring to do on the include
 > files, to make things cleaner, as there were some things that we
 > did not really like in the  end. As for moving to a -I compiler
 > option rather than relative pathnames in #include, that's a minor
 > change that would be welcome I think.

This work was supposed to be done after the changes that happened in 
October/November 2001.

  - Bruce



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf