+
+
+
+
+ 1.
+ |
+
+ How do I get GNOME 2.0 for FreeBSD?
+ |
+
+
+
+ |
+
+ There are two ways to install GNOME 2.0 on FreeBSD. One way is to use
+
+ packages, and the other way is to use
+
+ ports.
+
+ To install GNOME 2.0 from packages, use the command:
+
+ # pkg_add -r gnome2
+
+ This will download the latest GNOME 2.0 packages from the
+ FreeBSD FTP site, and proceed to install them on your system.
+ Note: Currently, building GNOME 2.0 from packages is
+ broken. GNOME 2.0 is still new, and work is being done to
+ improve the package installation process. You should instead
+ use the ports method below.
+
+ To build and install GNOME 2.0 from ports, you should first
+
+ cvsup the latest ports tree. Then:
+
+
+# cd /usr/ports/x11/gnome2
+# make clean
+# make install clean
+
+
+ After installing GNOME 2.0, you might consider adding the
+ following to /etc/make.conf:
+
+
+WITHOUT_GNOME=yes
+
+
+ This prevents applications that WANT_GNOME from installing
+ GNOME 1.4.1 components that conflict with GNOME 2.0. The GNOME
+ 1.4.1 and GNOME 2.0 desktops do not coexist. Work is being done
+ on the ports system to allow for GNOME 2.0 specific make macros,
+ but it has not been committed yet. For more on GNOME 1.4.1 and
+ GNOME 2.0 coexistence, please see the related
+ question below.
+ |
+
+
|
+
+
+
+
+ 2. |
+
+ GNOME 2.0 is failing to build from ports. What do I do?
+ |
+
+
+
+ |
+
+ The majority of GNOME 2.0 compilation problems can be solved
+ by making sure all the necessary GNOME 2.0 components are
+ up-to-date. You may see compiler errors relating to pthreads
+ (POSIX threads), such as:
+
+
+undefined reference to 'strerror_r'
+
+
+ To fix thread related errors, make sure you have the following
+ compiled into your kernel:
+
+
+options P1003_1B
+options _KPOSIX_PRIORITY_SCHEDULING
+
+
+ And make sure if you're tracking -stable or -current, that you
+ do not have NOLIBC_R set in
+ /etc/make.conf. If you do, remove it, then rebuild world.
+ If you still have trouble, please send email to
+
+ &email;@FreeBSD.org with the output of the failed compilation.
+ It is also helpful to include the config.log from the port's
+ work directory.
+
+ Ports such as devel/pth and devel/ngpt can
+ also cause pthread-related problems when compiling GNOME 2.0.
+ If you do not need these ports installed, it is recommended
+ you remove them.
+
+ |
+
+
|
+
+
+
+
+ 3. |
+
+ I installed GNOME 2.0, but I'm missing application foo.
+ What gives?
+ |
+
+
+
+ |
+
+ Only the core components, and a few extras, are included in the
+ gnome2 package. Since GNOME 2.0 is so new, there
+ haven't been a great deal of applications ported over to it.
+ As more applications become available, they will be ported
+ over. In the meantime, you can, however, run
+ GNOME 1.4.1 applications under GNOME 2.0.
+ |
+
+
|
+
+
+
+
+ 4. |
+
+ What's the best way to upgrade from GNOME 1.4.1 to GNOME 2.0?
+ |
+
+
+
+ |
+
+ Right now, the GNOME project is still very much in flux.
+ Work still must be done to the GNOME ports infrastructure in
+ order to get things working cleanly. However, if you have
+ GNOME 1.4.1, and you want to upgrade to GNOME 2.0, first
+ familiarize yourself with the official upgrade instructions from
+ the GNOME site. Next, make sure your GNOME 1.4.1 ports are
+ up-to-date, then remove the following GNOME 1.4.1 packages from
+ the system:
+
+
+gnomecore
+sawfish
+gnomeapplets
+gnomemedia
+gtop
+libgtop
+nautilus
+glade
+gedit
+xalf
+bugbuddy
+gnomegames
+gnomeutils
+
+
+ After those packages are removed, you can build GNOME 2.0 per the
+ instructions listed above.
+
+ |
+
+
|
+
+
+
+
+ 5. |
+
+ Can I install GNOME 1.4.1 applications under GNOME 2.0 and vice
+ versa?
+ |
+
+
+
+ |
+
+ Sure! To run GNOME 1.4.1 applications within the GNOME 2.0 desktop
+ you will need to have upgraded
+ from GNOME 1.4.1 to GNOME 2.0. Then, simply run the GNOME 1.4.1
+ application. Any GNOME 1.4.1 application that directly depends on
+ gnomecore (e.g. any panel applet) will not work in
+ GNOME 2.0 (e.g. gaim-gnome).
+
+ Upgrading GNOME 1.4.1 applications under GNOME 2.0 is currently
+ broken unfortunately. If gnomecore is installed, all bets are
+ off. This will result in GNOME 1.4.1 overwriting GNOME 2.0.
+ Fortunately, work is being done to correct this problem. As
+ soon as something is in place, this document will be updated.
+
+
+ To run GNOME 2.0 applications under GNOME 1.4.1, you will need
+ to make sure your GNOME 1.4.1 components are up-to-date, then
+ install the gnome2-devel port. To install this port
+ do the following:
+
+
+# cd /usr/ports/devel/gnome2-devel
+# make clean
+# make install
+
+
+ After installing the gnome2-devel port, you will
+ be able to install non-desktop GNOME 2.0 applications
+ (e.g. math/gcalctool).
+ |
+
+
|
+
+
+
+ 6. |
+
+ Where can I get more themes for GNOME 2.0?
+ |
+
+
+
+ |
+
+ The website
+ Sunshine in a Bag has been setup as a general GNOME theme
+ repository. They offer some gtk+-2.0, metacity, sawfish,
+ nautilus, and gdm themes, as well as some backgrounds.
+
+ See the instructions on the website for installing the themes.
+ If you feel inclined to port a few of them, you will not be
+ turned away ;-).
+ |
+
+
|
+
+
+
+
+ 7. |
+
+ What window managers work well with GNOME 2.0?
+ |
+
+
+
+ |
+
+ The gnome2 meta-port installs the
+ sawfish and
+ metacity window managers by default. Both
+ work quite well in GNOME 2.0. A lot of people prefer metacity
+ since it is lighter weight. However, sawfish will be used as
+ the default Window manager.
+ |
+
+
|
+
+
+
+ 8. |
+
+ Does GNOME 2.0 support anti-aliased fonts?
+ |
+
+
+
+
|
+
+ Yes! Anti-aliasing requires XFree86 4.x with
+ freetype2 support. To add freetype2 support to X, make
+ sure you have the following modules loaded in your
+ XF86Config file under the Modules section:
+
+
+Load "freetype"
+Load "type1"
+
+
+ Then, simply set the environment variable
+ USE_GDK_XFT to 1 before starting GNOME.
+ If you use gdm, you can add it to your ~/.gnomerc
+ file (make sure this file is executable!). If you use startx,
+ then add it to your ~/.xinitrc file.
+
+ If you have any questions, please send them to
+ &email;@FreeBSD.org.
+
+ |
+
+
|
+
+
+