Re: [q-lang-devel] Status of debian packaging

[<Dr....@t-...>]

Kari Pahula wrote:
> The nearest thing you got to a standard is the "Installing Info
> Directory Files" page in texinfo's doc and the dir-example file
> included with texinfo.  It has "Software development" category listed
> in it, Q would fit under that.  That'd be better than leaving it
> unspecified, IMHO.

Agreed. I'll add that in the next release.

> I've put packages of 5.1 at mentors.debian.net.  It's compiled now
> with -O3.

And Q 5.2 has just been released. ;-) It's only a couple of bug fixes 
this time, though.

> It's only for sid for now, but I'll try to find a sponsor for it and
> get it included in Debian proper.  That'll take care of having
> packages for sarge, too.  I wouldn't bother with backporting the
> package to woody, sarge should be released in the near future anyway.

Sounds good.

> I wouldn't bother to include readline with Q.  Trivial replacement for
> readline is scanf.  That's what I've seen other projects do.

Well, you're probably right, by now readline seems to be available 
almost everywhere.

> I wouldn't provide those --with-*-includes options.  The configure
> script is supposed to find the required flags without user
> intervention.  Ideally the only things the user should have to concern
> himself with are where to install (--prefix and friends) and what to
> install (--enable-* and --with-*).  And --with-libname is for a 'yes'
> or 'no' input from the user, not the flag to pass to the compiler.

Yes, that's exactly how my configure is supposed to work, too. I just 
added some functionality so I don't have to edit Makefiles and scripts 
just because, e.g., some lib is in /opt/sfw (SUN) or libpthread is 
actually called libc_r (FreeBSD). It's a convenience, and it doesn't 
break the standard --with-xyz={yes,no} behaviour, so why remove it?

> This is what dependency_libs in clib.la looks like in a pristine build:
> dependency_libs=' -L/home/kari/dl/q-5.1/libq /usr/local/lib/libq.la /usr/lib/libgmp.la -lpthread -lcrypt -lutil -lnsl -lm'

Ouch. Yes, this definitely has to be fixed. On the TODO list.

Thanks,
Albert

-- 
Dr. Albert Gr"af
Email:  Dr....@t-..., ag...@mu...
WWW:    http://www.musikwissenschaft.uni-mainz.de/~ag