"motiv4u" <[EMAIL PROTECTED]> writes:
> After extracting, there is an INSTALL file in the gnubg directory.
> However, for Ubuntu (and Xubuntu, Kubuntu), following the next scenario
> gives you a working gnubg build. 'sudo' will be used before the
> commands you're used to in other linux distro's.
It's worth noting that there is a gnubg package already in Debian (and
therefore probably also in Ubuntu) that I maintain, although it's a
package of the 0.15 snapshot rather than the current development source.
I plan on updating to the current development source (or ideally a 0.16
snapshot) as soon as we sort out a formal position of what's going on with
GPLv3 software.
If you want the trunk, the advantage of having a package already in Debian
is that all of this:
> First you need the additional packages and libraries.
> You'll get the packages like this:
> sudo apt-get install autoconf automake bison gcc gnuplot libtool make
> And the libraries:
> sudo apt-get install libartsc0-dev libatk1.0-dev libaudiofile-dev
> libcairo2-dev libesd0-dev libglib2.0-dev libgtk2.0-dev libgtkglextl-dev
> libpango1.0-dev libpng12-dev libreadline5-dev libxml2-dev python2.5-dev
can probably be replaced with:
apt-get build-dep gnubg
to install all the build dependencies of the existing gnubg package.
Although you may have to separately get the right Python.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
_______________________________________________
Bug-gnubg mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnubg
