|
|
楼主 |
发表于 2004-10-2 18:09:07
|
显示全部楼层
这里贴一贴README的内容，本人E文极差，看不懂,
GARNOME!
( the stable edition )
GARNOME -- the bad-ass, bleeding edge GNOME distribution for testers
and tweakers everywhere -- is finally released unto the teeming masses.
If you're dying to test the latest GNOME code, but don't want to fall
into the depraved addictions and co-dependencies of testing from
anonymous CVS, then GARNOME is for you.
What is GARNOME?
----------------
It's a bad-ass, bleeding edge GNOME distribution for testers and
tweakers everywhere. Those not paying attention can stay after class.
GARNOME is a distribution of GNOME, based on the [1]GAR ports system
by Nick Moffitt. It builds the latest GNOME Desktop tarball releases,
and includes extra GNOME 2.x software to provide testers with a
comfortable desktop environment.
Join our [2]mailing list! Read the [3]archives!
What is Stable GARNOME then?
----------------------------
Even though GARNOME is great for testers and bleeders, there are still
people who are stuck with, for whatever reason -- a machine with an old
version of GNOME (2.6, 2.4, 2.2, 2.0, even 1.4!) who might want to give
their desktop a dose of stability and sanity with the new improved
funkeyness of GNOME 2.8, without annoying their admins, teachers, staff
or anyone that doesn't care that you might want to run a desktop
that comes from this millenium.
Of course, this version of GARNOME is also useful for those people
who _are_ testing the standard version of GARNOME, especially if they
want something safe to return to if (or when) the development series
explodes.
What do I need to install GARNOME?
----------------------------------
First you'll have to [4]download GARNOME!
A sane GNU tool chain (gcc, make, flex, bison, gettext, patch, etc).
wget, gzip and bzip2.
The following basic libraries that GNOME depends on. Every
distribution should have these available or installed already.
For a basic, sane platform/ directory:
Debian Red Hat Linux
------ -------------
libpng3-dev libpng-devel
libjpeg-dev libjpeg-devel
libtiff-dev libtiff-devel
libncurses5-dev ncurses-devel
xlibs-dev XFree86-devel + XFree86-libs (or xorg-libs)
libpopt-dev popt
libbz2-dev, zlib1g-dev bzip2-devel
libexpat1-dev expat-devel
libsmbclient-dev samba
libhermes-dev Hermes-devel (via freshrpms.net)
docbook-xml + docbook-xsl docbook-dtds
openjade or jade openjade
For other GARNOME directories:
Debian Red Hat Linux
------ -------------
binutils-dev binutils + elfutils-libelf
libpcre3-dev pcre-devel
libgtkspell-dev pspell-devel
libmusicbrainz2-dev libmusicbrainz-devel (via freshrpms.net)
libltdl3-dev libtool-libs
libapm-dev apmd
libcupsys2-dev cups-devel
libgpgme-dev libgpgme-devel + libgpg-error-devel
libgnutls-dev gnutls-devel
libpisock-dev pilot-link-devel
libreadline4-dev readline-devel
libsensors-dev lm_sensors-devel
libldap2-dev openldap-devel
libopenh323-dev openh323-devel
libpt-dev pwlib-devel
libsdl-dev SDL-devel
python2.3-dev python-devel
valgrind valgrind (via dag.wieers.com)
Thanks to Kevin C. Krinke for providing the original Debian list we
based this from.
How do I configure GARNOME?
---------------------------
All the local settings are kept in gar.conf.mk. Here are the most
useful ones:
GARCHIVEDIR: If you've downloaded the tarball collection already,
point this to the directory your tarballs are in. Example:
GARCHIVEDIR = /home/pd/src/garnome/DOWNLOAD
main_prefix: Currently the default install location is $HOME/garnome.
If you'd prefer to install GARNOME elsewhere, change this entry.
How do I use GARNOME?
---------------------
Unpack the tarball, and optionally tweak the settings to your liking.
The defaults should work without problems, but please refer to the
'configuration' portion of this document for tips.
An IMPORTANT note about bootstrap/
----------------------------------
The number one question we get asked on the GARNOME list is about the
contents of the bootstrap/ directory. For those who don't know, this
directory contains programs that may or may not be present as part of an
installed system, but have garballs included for compatibility reasons.
The following systems _need_ things from bootstrap/
System Type Requires
----------- --------
Red Hat <= 7.3 render, xrender, freetype, fontconfig,
pkgconfig
Red Hat AS 2.1 freetype, fontconfig, pkgconfig
Mandrake <= 9.0 libiconv, pkgconfig
SuSE 9.x freetype, fontconfig
Mac OS X dlcompat, freetype, libiconv
The bootstrap/ directory works slightly differently to other directories,
to use it -- you need to enter each directory you need and type
'make install'.
For example, to compile on Mac OS X -- you would type:
cd bootstrap/dlcompat/
make install
(then repeat the process for the other packages you need)
A rule of thumb to use is:
'Unless you know you need something in bootstrap/, you don't!'
An IMPORTANT note about Linux, 2.6 kernels and GARNOME features
---------------------------------------------------------------
Since the release of GNOME 2.8.0, a number of features have been added to
the core GNOME desktop that allows enhanced filesystem features,
device-management and more.
The downside to this, is some portions of GNOME now depend on a 2.6.x or
newer kernel, as well as 'hal', 'dbus' and several other components.
If you are running an older distribution, this may mean that random
portions of the GARNOME desktop/ directory may not build.
To fix this, you have two options:
* Upgrade to a 2.6 kernel, and compile 'bootstrap/dbus' and 'bootstrap/hal'
or
* Remove the affected components
(currently only 'desktop/gnome-volume-manager') from your GARNOME build
by typing:
rm -rf desktop/gnome-volume-manager
Then resume your install by typing 'make install' in the desktop/
meta-directory.
Building GARNOME
----------------
Once you have determined if you need bootstrap/, simply return to the main
GARNOME directory and type:
cd desktop/
make paranoid-install
That's all there is to it! GARNOME will begin to build and install the
GNOME Desktop release, and everything it needs immediately.
If you want to build other meta directories or individual modules, just
change to the appropriate directory and type 'make paranoid-install' or
'make install' respectively.
'paranoid-install' is only available for meta garballs and will stop
building on the first error. Running 'make install' for a meta garball will
continue building on errors, trying to build other packages.
There is a lot of packages included in GARNOME that is not built as part of
the desktop/ category, including:
bindings/ GNOME platform bindings collection
fifth-toe/ A collection of high quality third-party programs
designed for your desktop, including Multimedia,
Graphics and Internet applications.
geektoys/ Various extensions to GARNOME that can enhance the
usability of your desktop, including new desktop
themes and applets that fit into an existing
installation.
hacker-tools/ Debuggers, Interface Designers and Hex Editors, oh my.
mono/ Mono(tm)
office/ Parts of the proposed 'GNOME Office' suite, including
a spreadsheet application, word processor and a
database application.
How do I start GARNOME once it is installed?
--------------------------------------------
The easiest way is to create a garnome-session script, and use the
standard method your distribution provides to launch it when you start
X. Here's what the script should look like:
#!/bin/sh
GARNOME=$HOME/garnome
PATH=$GARNOME/bin PATH
LD_LIBRARY_PATH=$GARNOME/libLD_LIBRARY_PATH
PYTHONPATH=$GARNOME/lib/python2.2/site-packages
PKG_CONFIG_PATH=$GARNOME/lib/pkgconfig:/usr/lib/pkgconfig
XDG_DATA_DIRS=$GARNOME/share
GDK_USE_XFT=1
LD_ASSUME_KERNEL=2.2.5
export PATH LD_LIBRARY_PATH PYTHONPATH PKG_CONFIG_PATH GDK_USE_XFT LD_ASSUME_KERNEL XDG_DATA_DIRS
exec $GARNOME/bin/gnome-session
Just set the GARNOME variable at the top to wherever you installed
GARNOME. It will usually be $HOME/garnome, as above.
If you start X with the startx command you should launch this in
~/.xinitrc. If you use the Xsession menu choice in GDM, you should
launch this in ~/.xsession. Assuming the garnome-session script is in
your path, both files should look like this:
#!/bin/sh
exec garnome-session
My own startup script is a little bit funkier:
#!/bin/sh
xset -solid black
if [ -e /home/pd/.fonts ]; then
xset fp+ /home/pd/.fonts/
xset fp rehash
fi
exec /usr/bin/ssh-agent /home/pd/garnome/bin/garnome-session & wmpid=$!
wait $wmpid
This sets the background to black so I don't have to look at the ugly
grey default for very long, sets up old X programs to use all the
fonts I have in my .fonts directory, and runs garnome-session under
ssh-agent (very useful if you use ssh keys) and then sits in the
background waiting for the session to conclude (useful for multiuser
and terminal based setups).
FAQ
---
BASIC QUESTIONS:
----------------
1. Can I install GARNOME without breaking my current GNOME setup?
Sure, that's part of what GARNOME is for! By default, it will
install to ~/garnome/ and not effect any of your existing GNOME
packages. It may affect your configuration files though, so you
ought to back them up or use a totally different user to run
GARNOME.
2. Can I install GARNOME over the top of my existing GNOME setup?
You could, but you shouldn't! (and we won't support you if you do)
GARNOME isn't a package based setup, it installs from GNOME tarballs
with patches. If you install GARNOME into /usr (for example), you will
overwrite your system setup with the software we provide.
All of your configuration will be overwritten, all of your settings
could vanish, all of the development libraries will be installed and
you will destroy any knowledge your packaging software (RPM, dpkg, etc)
has about your setup.
3. How long does GARNOME take to build?
On a Pentium III 1800, 512MB RAM system, building the GARNOME
2.8.0 desktop/ directory with time(1) returns:
real 93m26.111s
user 48m10.224s
sys 9m6.119s
On a Celeron 666 with 128MB RAM, the same install takes:
real 341m40.180s
user 225m11.216s
sys 35m1.111s
4. Can I speed up my GARNOME build?
Yes.
You can use ccache to speed up your GARNOME builds, although this
procedure requires additional disc space in your GARNOME build
directory.
Using ccache is a three step task, first you need to install
'bootstrap/ccache', then set your cache sizes, then configure your
gar.conf.mk file to use the cache.
GARNOME will require a different size cache depending on what parts
of it you choose to build, however, for best results -- setting your
cache size to 2GB by typing:
ccache -M 2G
Will be sufficently large to build all of the standard platform/ and
desktop/ garballs.
Once you have installed the software and set your cache size correctly,
open the gar.conf.mk file in the main GARNOME directory and uncomment
the lines relating to building with ccache.
note: If you are building bootstrap/mozilla, we recommend you make your
cache size 3GB -- otherwise, your cache may resize itself during the
build, which may evict some of the more important components of your
cache, slowing your build down.
5. Can I optimize my GARNOME build?
Yes.
Open the gar.conf.mk file in the main GARNOME directory and
look for the CC, CXX and CFLAGS lines -- uncomment these and
specify the flags that you need.
note: the best way to get a set of CFLAGS that will work with
your configuration is to use the cpucaps[7] program from the prompt,
you should see a line that says:
"Recommended gcc (version) target"
Uncomment and replace the CFLAGS line with the suggestions from that
line and restart your GARNOME build.
5. How much space does GARNOME require to build?
On an x86 system, GARNOME 2.8.0 (desktop category and its dependencies)
requires 2.5GB as build space (plus an additional 1GB if you are
building bootstrap/), however it only occupies 615MB once installed.
PRE-CONFIGURATION QUESTIONS:
----------------------------
1. GARNOME always fails on the checksums, are my tarballs broken?
Are you using GNU tools? Sometimes Sun's md5sum doesn't agree with
GARNOME's stored md5sums.
2. What is bootstrap/ for?
Please press 'Page Up' a few times and read the section entitled:
'An IMPORTANT note about bootstrap/'
BUILD QUESTIONS:
----------------
1. My build fails with:
"checking mach-o/dyld.h usability... no
checking mach-o/dyld.h presence... no
checking for mach-o/dyld.h... no
configure: error: No dyld.h found, can not continue
make[1]: *** [configure-work/main.d/dlcompat-20030629/configure] Error 1"
You are trying to compile dlcompat from bootstrap/ when you shouldn't be.
Please press 'Page Up' a few times and read the section entitled:
'An IMPORTANT note about bootstrap/' -- then type 'make install' from the
desktop/ directory.
2. My build fails in platform/glib with:
"gconvert.c:47:2: #error GNU libiconv not in use but included iconv.h
is from libiconv"
You are trying to compile libiconv from bootstrap/ when you shouldn't be.
Aside from pressing 'Page Up' a few times and reading the section
entitled: 'An IMPORTANT note about bootstrap/' -- you have three options:
a) delete iconv.h from your GARNOME prefix and continue your install
b) ensure your system includes path is before your GARNOME includes path
(usually not a good idea)
c) uncomment the libiconv dependancy in the platform/glib Makefile,
and 'make clean; make install' (only worth doing if you're on non-GNU
systems)
3. My build fails in platform/libgnomeprint with:
"checking for libgnomecups-1.0 >= 0.1.0...
Package libgnomecups-1.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libgnomecups-1.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libgnomecups-1.0' found"
If you have CUPS installed as the printing environment on your machine, you
should install the geektoys/libgnomecups package, which will solve this
problem.
3. My build fails in desktop/epiphany with:
"configure: error: Library requirements (mozilla-gtkmozembed) not met;
consider adjusting the PKG_CONFIG_PATH environment variable if your
libraries are in a nonstandard prefix so pkg-config can find them."
You don't have a suitable version of Mozilla installed on your system,
Epiphany and Galeon need Mozilla 1.7 or later to install correctly.
To solve this issue, you have two options:
a) install the relevant mozilla development packages for your system and
continue your install
b) uncomment the bootstrap/mozilla dependancy in the desktop/epiphany
Makefile, then run 'make clean; make install'
If you choose option b), then you need to add the mozilla libraries
installed in $GARNOME/lib/mozilla-<version> to your LD_LIBRARY_PATH,
otherwise Gaim and Evolution will not compile for you.
4. My build fails in desktop/nautilus with:
"nautilus-image-properties-view.c:134:96: macro "exif_content_get_value" passed 4 arguments, but takes just 2
nautilus-image-properties-view.c: In function `exif_content_callback':
nautilus-image-properties-view.c:134: `exif_content_get_value' undeclared (first use in this function)
nautilus-image-properties-view.c:134: (Each undeclared identifier is reported only once
nautilus-image-properties-view.c:134: for each function it appears in.)
make[6]: *** [nautilus-image-properties-view.lo] Error 1"
You are probably trying to compile nautilus with the libexif 0.6.x specific
patch.
You should edit the desktop/nautilus Makefile and comment out the PATCHFILES
line, before running 'make clean; make install' in the nautilus directory.
6. My build fails with:
"/usr/bin/install: cannot stat `./html/index.sgml': No such file
or directory"
There are two solutions, in order of "most correct" to "quickest":
a) Find out why gtkdoc-mkdb is failing. It's usually a b0rked or
non-existant docbook-dsssl install.
b) In gnome/category.mk, change --enable-gtk-doc to
--disable-gtk-doc. Run make clean and make install again.
If you install the correct software however, or help port our
documentation from SGML to XML, you will never have this problem
again. They have to be the best solutions, really. :-)
5. Scrollkeeper seems to hang when running scrollkeeper-update.
Yes, it's okay. You just have to wait a while for it to finish
processing (sometimes a long while). Nothing to be alarmed about.
6. My gnome-session and Nautilus segfault immediately, what's wrong?
See [5]bug 70351 at bugzilla.gnome.org.
7. GARNOME fails to build [insert failure here] on Debian Stable/Testing
Mostly, these errors are due to GCC 2.95 incompatibilities.
Again, ranging from "most correct" to "quickest" -- your solutions are:
a) File a bug against the package in question and make sure the
[2]Mailing List is on the CC list so that we can pick up any patches
that may appear.
b) Install GCC 3.2.3 or later from Debian Testing
8. GARNOME fails to build [insert failure here] on Red Hat 7.3, 8, 9, EL3
There are some components that fail to build in Red Hat, the two main
issues are:
* OpenSSL / Kerberos
These packages are both affected by Red Hat's packaging of OpenSSL and the
Kerberos 5 libraries. According to [6]this post -- Red Hat's opinion seems
to be a need to have these packages require pkg-config. Unfortunately,
some earlier OpenSSL installations don't have the .pc support for
pkg-config niceness, so hacking the GARNOME makefiles to support .pc files
_might_ work, but you may need to do post-OpenSSL-buggery if your
distribution is RH7.3, 8 or an unpatched version of 9.
Thus, none of the solutions are particularly "clean" -- but in a pinch:
a) exporting a PKG_CONFIG_PATH variable that points to your GARNOME install
_before_ the system path ('PKG_CONFIG_PATH=/home/pd/lib/pkgconfig:/usr/lib')
b) Adding the krb5 directory (--with-krb5=/usr/kerberos)
to the configure arguments in the Makefile in both the 'office/evolution',
'office/ximian-connector' and 'fifth-toe/gaim' directories.
* Binutils (RH9 only)
Red Hat 9 refuses to build 'ghex' because the ghex build doesn't recognize
'libbfd-2.13.90.0.18.so' as a valid linkable library. Adding a symlink
from '/usr/lib/libbfd-2.13.90.0.18.so' to '/usr/lib/libbfd.so' is the
easiest fix for this issue.
POST-INSTALL QUESTIONS:
-----------------------
1. I can see icons on my desktop, but no fonts?
You will need to build freetype, xrender and xft from the bootstrap/
directory, then restart your GARNOME session to have fonts displayed
correctly.
2. I can see fonts on my desktop, but no icons?
You need to build hicolor-icon-theme and shared-mime-info from the
bootstrap/ directory and add (if it doesn't exist) the XDG_DATA_DIRS
line to your GARNOME startup script.
3. How do I use anti-aliased fonts?
Set the GDK_USE_XFT environment variable. eg.: export GDK_USE_XFT=1
4. Where did my evolution/ directory go?
As part of the upgrade to Evolution 2.0, the import wizard will copy
your Evolution directory to ~/.evolution.
The GARNOME maintainers recommend you keep a copy of your existing
~/evolution directory (if it exists), until you decide that you
no longer need it.
5. Who do I talk to about GARNOME?
Join our [2]mailing list, or visit #garnome on irc.gnome.org.
References
----------
1. http://www.lnx-bbc.org/garchitecture.html
2. http://mail.gnome.org/mailman/listinfo/garnome-list
3. http://mail.gnome.org/archives/garnome-list/
4. http://cipherfunk.org/garnome/
5. http://bugzilla.gnome.org/show_bug.cgi?id=70351
6. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=82369
7. http://members.jcom.home.ne.jp/jacobi/linux/softwares.html |
|
IP卡
狗仔卡
发表于 2004-10-2 18:05:30
提升卡
置顶卡
沉默卡
喧嚣卡
变色卡
显身卡