[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
gnue/docbook/HowTos GNUe-SuSE-HOWTO.sgml
From: |
Derek Neighbors |
Subject: |
gnue/docbook/HowTos GNUe-SuSE-HOWTO.sgml |
Date: |
Thu, 14 Nov 2002 01:38:47 -0500 |
CVSROOT: /home/cvs
Module name: gnue
Changes by: Derek Neighbors <address@hidden> 02/11/14 01:38:45
Modified files:
docbook/HowTos : GNUe-SuSE-HOWTO.sgml
Log message:
New update to SuSE HowTo
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/docbook/HowTos/GNUe-SuSE-HOWTO.sgml.diff?cvsroot=OldCVS&tr1=1.1&tr2=1.2&r1=text&r2=text
Patches:
Index: gnue/docbook/HowTos/GNUe-SuSE-HOWTO.sgml
diff -c gnue/docbook/HowTos/GNUe-SuSE-HOWTO.sgml:1.1
gnue/docbook/HowTos/GNUe-SuSE-HOWTO.sgml:1.2
*** gnue/docbook/HowTos/GNUe-SuSE-HOWTO.sgml:1.1 Sat Oct 19 22:50:24 2002
--- gnue/docbook/HowTos/GNUe-SuSE-HOWTO.sgml Thu Nov 14 01:38:45 2002
***************
*** 3,12 ****
<article><!-- LyX 1.2 created this file. For more info see
http://www.lyx.org/ -->
<title>GNUe-SuSE-mini-HOWTO
</title><author>Arjen Runsink
! </author><date>v0.02, 17 October 2002
</date><abstract>This mini HOWTO describes how to get the GNUenterprise
packages
release 0.4.0 to work with the SuSE distribution version 8.0 and
! PostgreSQL or MySQL.
</abstract><toc><sect>Introduction
<p>While working with different projects and managing a few I found
I had much need to dig deeper into databases and all the possibilities
--- 3,12 ----
<article><!-- LyX 1.2 created this file. For more info see
http://www.lyx.org/ -->
<title>GNUe-SuSE-mini-HOWTO
</title><author>Arjen Runsink
! </author><date>v0.04, 11 November 2002
</date><abstract>This mini HOWTO describes how to get the GNUenterprise
packages
release 0.4.0 to work with the SuSE distribution version 8.0 and
! 8.1 inc combination with for example PostgreSQL or MySQL.
</abstract><toc><sect>Introduction
<p>While working with different projects and managing a few I found
I had much need to dig deeper into databases and all the possibilities
***************
*** 24,36 ****
<p>This is the first version. I don't know if I am ready with it.
Maybe things don't work in the end. If you have something I might
add, or a correction send me an email: arjen(*a*t*)zeilers.net
- </p><p>$Id: GNUe-SuSE-HOWTO.lyx,v 1.2 2002/10/17 17:07:25 arjen
- Exp arjen $
</p><sect>Getting the raw materials
<p>To start of let's get all that is needed.
</p><sect1>The GNUe Packages
! <p>The GNUe packages are quite they can be downloaded from <url
url="http://www.gnue.org" name="www.gnue.org">. See
! the download section.
</p><p>GNUe-Common-0.4.0.tar.gz
</p><p>GNUe-Designer-0.4.0.tar.gz
</p><p>GNUe-Forms-0.4.0.tar.gz
--- 24,34 ----
<p>This is the first version. I don't know if I am ready with it.
Maybe things don't work in the end. If you have something I might
add, or a correction send me an email: arjen(*a*t*)zeilers.net
</p><sect>Getting the raw materials
<p>To start of let's get all that is needed.
</p><sect1>The GNUe Packages
! <p>The GNUe packages can be downloaded from <url url="http://www.gnue.org"
name="www.gnue.org">. See the download section.
!
</p><p>GNUe-Common-0.4.0.tar.gz
</p><p>GNUe-Designer-0.4.0.tar.gz
</p><p>GNUe-Forms-0.4.0.tar.gz
***************
*** 43,49 ****
<p>Egenix-mx-base provides, amongst some other stuff, the mxDateTime
which could not be found anymore, the INSTALL that comes with GNUe
mentions it, and that it possibly could be provided with python 2.1+.
! Well SuSE 8.0 comes with python 2.2 but no mxDateTime.
</p><p>You can get the package at <url
url="http://www.lemburg.com/python/mxExtensions.html"
name="http://www.lemburg.com/python/mxExtensions.html">
</p><p>The file I used was egenix-mx-base-2.0.4.tar.gz
</p><sect1>wxPythonSrc
--- 41,48 ----
<p>Egenix-mx-base provides, amongst some other stuff, the mxDateTime
which could not be found anymore, the INSTALL that comes with GNUe
mentions it, and that it possibly could be provided with python 2.1+.
! Well SuSE 8.0 comes with python 2.2 but no mxDateTime. For SuSE 8.1
! it is more easy. The package is included with the distribution.
</p><p>You can get the package at <url
url="http://www.lemburg.com/python/mxExtensions.html"
name="http://www.lemburg.com/python/mxExtensions.html">
</p><p>The file I used was egenix-mx-base-2.0.4.tar.gz
</p><sect1>wxPythonSrc
***************
*** 66,71 ****
--- 65,72 ----
m4 binutils autoconf automake glib-devel \
glibc-devel gtk-devel python python-devel \
postgresql-python sablot sablot-devel pyxml
+ #for SuSE 8.1 add python-egenix-mx-base
+
</verb></p><p>This list may not be complete. Perhaps not all dependencies for
these packages are listed, but that is OK, yast will resolve them
automatically. If I forgot something, a compile will stop and complain
***************
*** 91,99 ****
</p><p><verb>tar -xvzf ˜/DOWNLOADS/GNUe/egenix-mx-base-2.0.4.tar.gz
cd egenix-mx-base-2.0.4
python setup.py build
! su -c "python setup.py install"
! </verb></p><p>su asks for the <em>root</em> password, type it in and the lot
is installed
! as root
</p><sect1>wxPythonSrc
<p>I chose to install wxPython with it's own wxGTK version that
came with it. SuSE does come with its own version of wxGTK which
--- 92,110 ----
</p><p><verb>tar -xvzf ˜/DOWNLOADS/GNUe/egenix-mx-base-2.0.4.tar.gz
cd egenix-mx-base-2.0.4
python setup.py build
! su -c "checkinstall python setup.py install"
! </verb></p><p>Now su asks for the <em>root</em> password, type it in.
Normally instead
! of su -c checkinstall one would use make install or in this case
! python setup.py install. Checkinstall does a make install and generates
! an rpm. It asks a few details and then creates and installs the rpm
! and also saves it in /usr/src/packages/RPMS/i386. I use checkinstall
! because it is easy to make an unofficial rpm so the installed files
! can be easily removed without needing the source tree to do a make
! uninstall or installed on another host. And very few packages provide
! a make uninstall. This reduces clutter immensely. Checkinstall has
! lot's of nice options and the packages can be tailored even more
! than described in this document. Do a checkinstall --help for more
! info.
</p><sect1>wxPythonSrc
<p>I chose to install wxPython with it's own wxGTK version that
came with it. SuSE does come with its own version of wxGTK which
***************
*** 125,140 ****
make allmo
cd ../build
su -c checkinstall
! </verb></p><p>Again su asks for the <em>root</em> password. Normally instead
of su -c
! checkinstall one would use make install. Checkinstall does a make
! install and generates an rpm. It asks a few details and then creates
! and installs the rpm and also saves it in /usr/src/packages/RPMS/i386.
! </p><p>I use checkinstall because it is easy to make an unofficial rpm
! so the installed files can be easily removed or installed on another
! host without needing the source tree to do a make uninstall. And
! very few packages provide a make uninstall. This reduces clutter
! immensely.s and GNUe-Navigator
! </p><p>Configuring GNUe
</p><p>Checkinstall asks a few questions. First if it should generate
some default documentation. Just say yes. As a description I gave
<em>wxGTK for wxPython.</em>
--- 136,142 ----
make allmo
cd ../build
su -c checkinstall
! </verb></p><p>Again su asks for the <em>root</em> password.
</p><p>Checkinstall asks a few questions. First if it should generate
some default documentation. Just say yes. As a description I gave
<em>wxGTK for wxPython.</em>
***************
*** 153,159 ****
python setup.py build IN_CVS_TREE=1\
WX_CONFIG=$WXPREF/bin/wx-config \
BUILD_GLCANVAS=0 BUILD_XRC=1
! su -c "python setup.py install IN_CVS_TREE=1\
WX_CONFIG=$WXPREF/bin/wx-config \
BUILD_GLCANVAS=0 BUILD_XRC=1"
</verb></p><p>Afaik you can not use checkinstall (yet) to install wxPython.
--- 155,161 ----
python setup.py build IN_CVS_TREE=1\
WX_CONFIG=$WXPREF/bin/wx-config \
BUILD_GLCANVAS=0 BUILD_XRC=1
! su -c "checkinstall python setup.py install IN_CVS_TREE=1\
WX_CONFIG=$WXPREF/bin/wx-config \
BUILD_GLCANVAS=0 BUILD_XRC=1"
</verb></p><p>Afaik you can not use checkinstall (yet) to install wxPython.
***************
*** 173,179 ****
</p><p><verb>tar -xvzf ˜/DOWNLOADS/GNUe/PySablot-0.1.tar.gz
cd PySablot-0.1
python setup.py build
! su -c 'python setup.py install'
</verb></p><p>And that's it.
</p><sect1>The GNUe packages
<p>All the packages depend on Common so install that one first.
--- 175,181 ----
</p><p><verb>tar -xvzf ˜/DOWNLOADS/GNUe/PySablot-0.1.tar.gz
cd PySablot-0.1
python setup.py build
! su -c 'checkinstall python setup.py install'
</verb></p><p>And that's it.
</p><sect1>The GNUe packages
<p>All the packages depend on Common so install that one first.
***************
*** 195,201 ****
</verb></p><p>Why edit setup.cfg.in instead of setup.cfg? Well the last is
overwritten by the first during the build phase.
</p><p><verb>python setup.py build
! su -c "python setup.py install"
</verb></p><p>And ignore the warning about the fact that the modules were not
installed in a path that is in Python's module search path.
</p><p>Repeat these steps for the modules GNUe-Designer, GNUe-Forms,
--- 197,203 ----
</verb></p><p>Why edit setup.cfg.in instead of setup.cfg? Well the last is
overwritten by the first during the build phase.
</p><p><verb>python setup.py build
! su -c "checkinstall python setup.py install"
</verb></p><p>And ignore the warning about the fact that the modules were not
installed in a path that is in Python's module search path.
</p><p>Repeat these steps for the modules GNUe-Designer, GNUe-Forms,
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- gnue/docbook/HowTos GNUe-SuSE-HOWTO.sgml,
Derek Neighbors <=