Re: What good are the logs?

2000-05-25 Thread Dave Peticolas
> Sorry to ask a stupid question, but what good are the logs that GnuCash > writes out? They have lots of information, but I can't see any convenient > way to use it (without doing some programming). > > In particular, when I forget to quit GnuCash before quitting X, I seem > to get a log file b

Re: The Library Problem

2000-05-25 Thread Glen Ditchfield
On Thu, 25 May 2000, Bill Gribble wrote: > And what if the user doing the install isn't root and can't even write > in /usr/local? ... There needs to be some way to re-root the > install at install time so that you can put gnucash under an arbitrary > directory without re-configuring and re-build

What good are the logs?

2000-05-25 Thread Dylan Paul Thurston
Sorry to ask a stupid question, but what good are the logs that GnuCash writes out? They have lots of information, but I can't see any convenient way to use it (without doing some programming). In particular, when I forget to quit GnuCash before quitting X, I seem to get a log file but no saved

Re: missing xml, print; 1.3.7, SuSE

2000-05-25 Thread Hendrik Boom
> gnome-print is in series gnm: gnprint and gnprintd > > I added these (yet another) dependencies to SuSE-6.3.txt. > (Perhaps we should recommend to buy a new big harddisk and > just install the whole 6 CDROMs ;-).) > > Dave: Please add the attached SuSE-6.3.txt to CVS. > > Herbert. Thanks. I

1.3.7 compile problems (g-wrap)

2000-05-25 Thread Matthew Vanecek
Is the list still active. The list archives seem to have stopped at March for some reason, so I was not sure... 1.3.7 won't compile. So far, it's due to problems with g-wrap-guile. I futzed with configure so it won't look for swig (why is that still in there--a message from March said y'all ne

Re: missing xml, print; 1.3.7, SuSE

2000-05-25 Thread Dave Peticolas
> > BTW: For what is XML used in GnuCash? XML is not used by GnuCash directly, it's used by the gnome libraries that are linked to GnuCash. I think it's used by the gnome-print library, though what for I don't know. dave

Re: missing xml, print; 1.3.7, SuSE

2000-05-25 Thread Herbert Thoma
> > When compiling 1.3.7 on SuSE 6.3, it could not find two libraries: > > > > xml > > print > > > > When I installed packages libxml (and libxmld too, just in case) > > from series d, the xml problem went away (although I had to delete > > the source tree and reuntar it to make it

Re: The Library Problem

2000-05-25 Thread Garrett Robert Banuk
Yes, I've thought about doing this. Maybe on my free time over this summer. I was going to do this for my college project but it just seems to small. It would really help to get people to migrate over to linux. Well this is getting off topic for this list... On 25 May 2000, Bill Gribble wrote:

Re: The Library Problem

2000-05-25 Thread Bill Gribble
Garrett Banuk <[EMAIL PROTECTED]> writes: > Maybe have 2 or 3 versions of gnucash. Source, binary and statically > linked everything binary for a the linux newbies who wouldn't know how to > install everything else. It may be unrealistic, but I would like an install experience that's as novice-

Re: The Library Problem

2000-05-25 Thread Garrett Banuk
Maybe have 2 or 3 versions of gnucash. Source, binary and statically linked everything binary for a the linux newbies who wouldn't know how to install everything else. At 06:48 PM 5/25/00 +0200, T.Pospisek's MailLists wrote: >I think your problem is a fundamental one. It's the same problem **al

Re: The Library Problem

2000-05-25 Thread T.Pospisek's MailLists
I think your problem is a fundamental one. It's the same problem **all** the commercial vendors have, whether they use gnome or not. See f.ex. StarOffice which was (still is?) statically linked even against the most basic labraries. It's what the LSB is about and here for (www.linuxbase.org). *t

Re: The Library Problem

2000-05-25 Thread Bill Gribble
Christopher Browne <[EMAIL PROTECTED]> writes: > It seems to me to make sense to use the appropriate dependancy management > system for differing Linux and BSD systems. If we build our own, all > we accomplish is to force an extra packaging system that will conflict > with the "native" one (e.g.