diff --git a/en/gnome/docs/bugging.sgml b/en/gnome/docs/bugging.sgml index d63cd215ca..963ed8ac46 100644 --- a/en/gnome/docs/bugging.sgml +++ b/en/gnome/docs/bugging.sgml @@ -1,123 +1,124 @@ - + + ]> &header;

1. When should I make a bug report?

2. What to report?

Always report as much information as you can. Too much information is always preferable to too little information. Superfluous information can be filtered out; developers like to play guessing games with code, not with bug reports.

A good bug report should at least include the following information:

If you have a solution or a workaround for the problem, then include it into your report as well, even if you are not quite sure that it is a proper fix. Even if the fix is not quite right, it could still point others in the right direction.

3. Where to report?

Once you are sure it is a new problem, there are several ways to report a bug in GNOME running on FreeBSD: you could send a report to the freebsd-gnome mailing list, file a problem report in the FreeBSD bug reporting system, send your report to the application's developers via the GNOME bug tracking system, or any combination of those.

&footer; diff --git a/en/gnome/docs/develfaq.sgml b/en/gnome/docs/develfaq.sgml index 881295cbdb..38a3634619 100644 --- a/en/gnome/docs/develfaq.sgml +++ b/en/gnome/docs/develfaq.sgml @@ -1,172 +1,173 @@ - + + ]> &header;

Contents

  1. What are development versions of GNOME all about?
  2. Should I track development versions?
  3. How do I obtain development versions of GNOME stuff?
  4. How do I keep everything up-to-date and in sync?
  5. What should I do when something does not work?
  6. How can I help with the development versions?
  7. What is the current state of development GNOME on FreeBSD

Full Text

  1. What are development versions of GNOME all about?

    The development versions are the packages released by the GNOME project that will eventually become the stable (release) versions. There are three working branches of GNOME development:

    1. STABLE - The applications and libraries in the stable branch are considered "release quality," and are the versions that appear in the FreeBSD ports tree. The current stable version is GNOME &gnomever;.
    2. DEVELOPMENT - In between stable releases are development releases. Traditionally, GNOME development releases have odd minor numbers (e.g. 2.3, &gnomedevelver;, 2.(n*2)-1). Development releases will become stable releases, and move from alpha to beta quality during their lifecycle. The development releases need testing by FreeBSD users to minimize the number of surprises when the new stable versions are committed to the FreeBSD CVS tree. This document is about the development branch. The current development branch is GNOME &gnomedevelver;.
    3. CVS - Often newer-than-new, the CVS HEAD versions of GNOME applications and libraries are alpha quality, or often completely unbuildable. The FreeBSD GNOME project pays attention to, but does not track the alpha quality code.

  2. Should I track GNOME development versions?

    If you are looking for a stable environment, absolutely not. Please only track the GNOME &gnomedevelver; branch if you wish to help identify bugs and improve the FreeBSD GNOME project. You will find little sympathy if a development-quality GNOME application eats your homework.

  3. How do I obtain the development versions of GNOME stuff?

    Marcus maintains a CVS repository where all the development versions of the GNOME components for FreeBSD are housed. Instructions for how to check out the development ports module and how to merge it into the FreeBSD ports tree reside on the entrance page to his repository. Please read carefully the instructions at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi.

    During the development cycle, FreeBSD-specific caveats and other useful information will be sent to marcuscom-devel@marcuscom.com. If you are tracking the GNOME development branch, you must subscribe to this list. You should also consider subscribing to &email;@FreeBSD.org.

    In order to help with bug reports, be sure to add the following to /etc/make.conf so that gdb back traces contain useful information:

     WITH_DEBUG=yes

    GNOME has an excellent guide for getting useful back traces.

  4. How do I keep everything up-to-date and in sync?

    The short answer is that you need to use the marcusmerge script to merge the development tree with the FreeBSD ports tree. The marcusmerge script is available here, and a man page on using the script is available here. This script will merge the development ports tree into your main ports tree. From there, you can use portupgrade to upgrade from &gnomever; to &gnomedevelver; and stay up-to-date afterwards. NOTE: if this is a first-time upgrade from &gnomever; to &gnomedevelver; you must run a special portupgrade command to account for the move from X11BASE to LOCALBASE:

     portupgrade -rf glib-2\* cairo gnome-doc-utils gnome-mime-data gnome-audio

    The long answer is that keeping up-to-date with the GNOME development branch is complicated. Sometimes components change in a way that makes portupgrade fail, or causes strange end results. If you plan to track the development branch, it is a good idea to join the freebsd-gnome mailing list, as well as to join the #freebsd-gnome IRC channel on FreeNode (irc.freenode.net).

    If all of this sounds scary, or you need a desktop that "Just Works," you should stick with the stable GNOME branch.

  5. What should I do when something does not work?

    It depends. If you think the problem is truly a bug with the GNOME component, you can report a bug using bug-buddy or the GNOME Bugzilla interface. If you think the problem lies in a FreeBSD port, or is FreeBSD-specific, send email to &email;@FreeBSD.org, or report the problem on the #freebsd-gnome IRC channel on FreeNode.

    Please forward all relevant bug IDs to &email;@FreeBSD.org so we can keep track of known issues. Thanks!

  6. How can I help with the development versions?

    Now that work on &gnomedevelver; has started, we need people to install it, and test things. If you are compiling &gnomedevelver; by hand, be sure to build debugging symbols. Package users will have these symbols already.

  7. What is the current state of development GNOME on FreeBSD?

    GNOME 2.17.2 is now out, and ports and packages are up-to-date. Keep those bug reports coming.

&footer; diff --git a/en/gnome/docs/example-Makefile.sgml b/en/gnome/docs/example-Makefile.sgml index c2c62c413d..afd8320da7 100644 --- a/en/gnome/docs/example-Makefile.sgml +++ b/en/gnome/docs/example-Makefile.sgml @@ -1,68 +1,69 @@ - + + ]> &header;

The following is an example Makefile for a FreeBSD GNOME port.

 # New ports collection makefile for:	gnomeapp
 # Date created:						27 December 2003
 # Whom:								Some GNOME User <&email;@FreeBSD.org>
 #
-# $FreeBSD: www/en/gnome/docs/example-Makefile.sgml,v 1.11 2006/08/19 21:20:35 hrs Exp $
+# $FreeBSD: www/en/gnome/docs/example-Makefile.sgml,v 1.12 2006/10/14 17:13:19 marcus Exp $
 #
 
 # For this example, assume there was already a gnomeapp in the tree, and that this
 # is the GTK+-2 version (i.e. gnomeapp2 versus gnomeapp).
 PORTNAME=		gnomeapp2
 PORTVERSION=	&gnomever;.2
 MASTER_SITES=	${MASTER_SITE_GNOME}
 MASTER_SITE_SUBDIR= sources/${PORTNAME:S/2//}/${PORTVERSION:C/^([0-9]+\.[0-9]+).*/\1/}
 DISTNAME=	${PORTNAME:S/2//}-${PORTVERSION}
 DIST_SUBDIR=	gnome2
 
 MAINTAINER=	gnome@FreeBSD.org
 COMMENT=	A GNOME app that does some stuff
 
 USE_BZIP2=	yes
 USE_XLIB=	yes
 GNU_CONFIGURE=	yes # NOTE: if the port needs ltverhack, this must be
 USE_AUTOTOOLS=libtool:15
 USE_GMAKE=		yes # same with GNU make
 # This is for i18n:
 CONFIGURE_ENV+=	CPPFLAGS="-I${LOCALBASE}/include" \
 				LDFLAGS="-L${LOCALBASE}/lib"
 USE_GNOME=		gnomehack gnometarget gtk20
 
 # This application can dock in the GNOME panel, or it can not.
 # But there's no need to build support for it if the GNOME panel
 # libraries are not installed, so only build GNOME panel support
 # if the gnomepanel port is already installed.
 WANT_GNOME=		yes
 
 .include <bsd.port.pre.mk>
 
 .if ${HAVE_GNOME:Mgnomepanel}!=""
 USE_GNOME+= 		gnomepanel
 CONFIGURE_ARGS+=    --with-gnome
 PKGNAMESUFFIX=  	-gnome
 .else
 CONFIGURE_ARGS+=    --without-gnome
 .endif
 
 # Given all the above code, the package name is either "gnomeapp2-gnome-&gnomever;.2" or
 # "gnomeapp2-&gnomever;.2", depending upon whether you want gnomepanel support. The downloaded
 # distfile will be "gnomeapp-&gnomever;.2.tar.bz2."
 
 .include <bsd.port.post.mk>
&footer; diff --git a/en/gnome/docs/faq2.sgml b/en/gnome/docs/faq2.sgml index ec06c77354..5c345de7d7 100644 --- a/en/gnome/docs/faq2.sgml +++ b/en/gnome/docs/faq2.sgml @@ -1,1155 +1,1156 @@ - + + ]> &header;

Contents

  1. How do I get GNOME &gnomever; for FreeBSD?
  2. How do I get the most out of GNOME?
  3. GNOME &gnomever; is failing to build from ports. What do I do?
  4. I installed GNOME &gnomever;, but I am missing application foo. What gives?
  5. What is the best way to upgrade from GNOME &gnomeoldver; to GNOME &gnomever;?
  6. How do I keep my GNOME &gnomever; components and applications up-to-date?
  7. How do I uninstall GNOME?
  8. Where can I get more themes for GNOME &gnomever;?
  9. What window managers work well with GNOME &gnomever;?
  10. Does GNOME &gnomever; support anti-aliased fonts?
  11. How can I control what fonts are anti-aliased?
  12. How do I edit my GNOME 2 menus?
  13. How do I use GTK+ 2 resource settings for GTK+ 2 applications when not in a GNOME environment?
  14. How do I configure settings for GNOME 1.4 applications under GNOME &gnomever;?
  15. Nautilus-cd-burner does not let me burn CDs, or Totem/Goobox/Sound-juicer cannot find my CD/DVD drive. How can I fix this?
  16. How do I add new GDM sessions?
  17. How do I disable spatial Nautilus?
  18. How do I disable desktop icons for "Computer," "Home," and "Trash?"
  19. How do I mount my removable media in Nautilus?
  20. Why is GNOME so slow to start up?
  21. How do I install GNOME packages from the GNOME Tinderbox?
  22. How do I add new MIME types to GNOME?
  23. How do I configure GDM for automatic logins?
  24. How do I upgrade from gnome2-lite to the full GNOME &gnomever; desktop?
  25. How do I enable Emacs-style keybindings in GTK+ applications?
  26. Why do I only see generic icons in Nautilus?
  27. Why do I need confirm access to my keyring every time Nautilus tries to open an external share?

Full Text

  1. How do I get GNOME &gnomever; for FreeBSD?

    There are two ways to install GNOME &gnomever; on FreeBSD. One way is to use packages, and the other way is to use ports. Before doing either installation, you should first familiarize yourself with the GNOME &gnomever; release notes.

    Install GNOME &gnomever; from packages.

    To install GNOME &gnomever; from packages, use the command:

    # pkg_add -r gnome2

    This will download the latest GNOME &gnomever; packages from the FreeBSD FTP site, and proceed to install them on your system.

    Up-to-date GNOME packages for i386 and amd64 for all supported versions of FreeBSD are also available from the GNOME Tinderbox.

    To build GNOME &gnomever;, you must first obtain the latest ports tree skeleton. This is most easily accomplished with portsnap(8) or cvsup. Then:

     # cd /usr/ports/x11/gnome2
 # make clean
 # make install clean

    Make GNOME &gnomever; start when X starts.

    Once you have the GNOME &gnomever; desktop installed, GNOME &gnomever; can be started by adding the following line to ~/.xsession or ~/.xinitrc, as appropriate:

     exec gnome-session

  2. How do I get the most out of GNOME?

    In order to make the most of your new GNOME Desktop, you will want to start all of the GNOME-related services at boot-time. If you wish to take full advantage of GNOME, add the following to /etc/rc.conf:

     gnome_enable="YES"

    This will enable services such as GDM, HAL, D-BUS, and Avahi. If you do not want to run all of these services, you should forgo the gnome_enable property, and manually enable the services you want.

  3. GNOME &gnomever; is failing to build from ports. What do I do?

    The majority of GNOME &gnomever; compilation problems can be solved by making sure all the necessary GNOME &gnomever; components are up-to-date.

    Updating solves most problems

    If you have not yet followed FAQ #6, do so, as it will most likely fix the problem you are reading this document to solve.

    Please follow FAQ #6. If you have not done so, and you ask for help, you will be told to follow FAQ #6.

    In general, when a GNOME &gnomever; component is not up-to-date, you will see an error similar to the following:

     checking for libgnomeui-2.0 libbonoboui-2.0 libbonobo-2.0 >= 2.2.1
 gnome-vfs-2.0 libgnomeprint-2.2 >= 2.3.0 libgnomeprintui-2.2 libglade-2.0...
 configure: error: Library requirements (libgnomeui-2.0 libbonoboui-2.0
 libbonobo-2.0 >= 2.2.1 gnome-vfs-2.0 libgnomeprint-2.2 >= 2.3.0 libgnomeprintui-2.2
 libglade-2.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable
 if your libraries are in a nonstandard prefix so pkg-config can find them.

    Simply keeping your ports tree up-to-date will prevent these errors.

    If the pkg-config program is out-of-date, you may see a configure error similar to the following:

     configure: error: *** pkg-config too old; version 0.14 or better required.

    While this may be buried in some other text, the error is very straight-forward: you need to upgrade pkg-config. The pkg-config application is found in the devel/pkg-config port. By updating this port to the latest version, this error will go away.

    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     _KPOSIX_PRIORITY_SCHEDULING

    If you are tracking -STABLE or -CURRENT, make sure that you do not have NO_LIBPTHREAD 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.

    Prevent two versions of the same library.

    A common source of build failures is the existence of multiple versions of the same library. This can happen if you have two different versions of a port installed, or can even happen through normal portupgrade use. You can back up the libraries in /usr/local/lib/compat/pkg and remove them, and then run portupgrade -u -rf pkg-config. This will force a rebuild of all GNOME-related apps (and a fair number of other apps) without retaining old versions of libraries in /usr/local/lib/compat/pkg.

    Fix PREFIX move-related errors.

    Starting with 2.16, GNOME now lives in LOCALBASE instead of X11BASE. This move can cause strange build problems if the proper upgrade steps are not followed. However, if after following all the steps, you may still see errors like the following:

     grep: /usr/X11R6/lib/libglade-2.0.la: No such file or directory
 sed: /usr/X11R6/lib/libglade-2.0.la: No such file or directory
 libtool: link: `/usr/X11R6/lib/libglade-2.0.la' is not a valid libtool archive

    This error indicates that an old libtool archive (a file that ends with .la) is still lingering about on your system. To find such files, search through the system for libtool archive files that contain the bad string (/usr/X11R6/lib/libglade-2.0.la in the example above). To do that, use the following command:

     # find / -type f -name "*.la" | xargs grep -l /usr/X11R6/lib/libglade-2.0.la

    For each file that is found, use pkg_info to determine which port or package installed it. For example, if you find that /usr/X11R6/lib/libgnomeui-2.0.la contains the problem libtool reference, do the following:

     # pkg_info -W /usr/X11R6/lib/libgnomeui-2.0.la

    If you get back a package name, then force an upgrade of that package using portupgrade. If you do not get back anything, then you can safely delete the libtool archive file. Once the file is gone, check the directory from which you deleted it for other files with similar names. In the example above, check for /usr/X11R6/lib/libgnomeui-2.0.*. If you find any matching files, delete those, too. Once all of the files are gone, you can resume building your original port. Repeat these steps if you encounter further such problems.

  4. I installed GNOME &gnomever;, but I am missing application foo. What gives?

    Only the core desktop is included in the gnome2 package. Here are some other GNOME meta-ports that offer convenient groupings of popular GNOME 2 software.

    To install any of these from packages:

     # pkg_add -r meta-port

    For example, to install the GNOME 2 Fifth Toe from packages:

     # pkg_add -r gnome2-fifth-toe

    To install any of these from ports:

     # cd /usr/ports/category/meta-port
 # make clean
 # make install clean

    For example, to install the GNOME 2 Fifth Toe from ports:

     # cd /usr/ports/x11/gnome2-fifth-toe
 # make clean
 # make install clean

  5. What is the best way to upgrade from GNOME &gnomeoldver; to GNOME &gnomever;?

    The &gnomeoldver; to &gnomever; may have a few caveats. You are strongly advised to read the upgrade FAQ for detailed instructions.

  6. How do I keep my GNOME &gnomever; components and applications up-to-date?

    You are emphatically encouraged to use portupgrade or portmaster to keep your GNOME &gnomever; components and applications up-to-date.

    Update your ports with portupgrade or portmaster.

    Once you have updated your ports tree (presumably with cvsup), the following two simple commands will update what needs to be updated, and will prevent inconsistencies:

     # pkgdb -F
 # portupgrade -a

    OR

     # portmaster -a

    Start from scratch.

    Despite consistent utilization of portupgrade or portmaster, if it seems like everything is refusing to build with everything else, you might save yourself a headache or three by removing all your GNOME apps and reinstalling them (your data files will remain untouched). To do this, follow these commands:

     # pkg_delete -rf pkg-config\*
 # cd /usr/ports/x11/gnome2
 # make clean
 # make install clean

    After running the above commands, you will have to reinstall all the GNOME applications you desire. This process sounds painful, but it is actually a great way to clear cruft off of your system. Just install applications as you need them, and you will be surprised how much disk space you have reclaimed. A full rebuild does take a significant amount of time; fortunately, this measure is only rarely needed.

  7. How do I uninstall GNOME?

    We would prefer that you did not uninstall GNOME ;-), but if you must, you have to decide how much you want to uninstall. If you have installed x11/gnome2 and you want to remove all Desktop components that do not have other dependent packages, do the following:

     # pkg_deinstall -R x11/gnome2

    Note: the pkg_deinstall command requires you have ports-mgmt/portupgrade installed.

    If you want to force a removal of all Desktop components (this is generally not recommended), do the following:

     # pkg_deinstall -Rf x11/gnome2

  8. Where can I get more themes for GNOME &gnomever;?

    On the following websites, you can find themes for GTK+, metacity, nautilus, GDM, icons, backgrounds, and more:

    Some of these themes have already been ported to FreeBSD. Check out the x11-themes/gnome-icons and x11-themes/metacity-themes meta-ports for a nice sample.

  9. What window managers work well with GNOME &gnomever;?

    The gnome2 meta-port installs the metacity window manager by default. Another popular window manager that works well with GNOME &gnomever; is sawfish. Sawfish can be found in x11-wm/sawfish.

    To switch between metacity and sawfish in GNOME 2, you will need to do the following:

     # killall metacity; sawfish &
 # gnome-session-save --gui

    The gnome-session-save is important. Without it, the window manager will revert back to the one previously configured upon next login. To switch back, simply reverse sawfish and metacity.

    If you have gotten the GNOME &gnomever; desktop working under an alternative window manager, please take a screenshot and send it to us!

  10. Does GNOME &gnomever; support anti-aliased fonts?

    Yes! Anti-aliasing requires XFree86 4.x or X.Org with freetype2 support. To add freetype2 support to X, make sure you have the following modules loaded in your XF86Config or xorg.conf file under the Modules section:

     Load	"freetype"
 Load	"type1"

    Then, simply check out the Fonts capplet under Applications->Desktop Preferences. If you want a good set of TrueType starter fonts, install the x11-fonts/webfonts port.

    Sometimes, after adding new fonts to the system, it is necessary to teach fontconfig about them. If you find that newly added fonts are not made available even after restarting GNOME 2, run the following command as root:

     # fc-cache -f -v

    If you have any questions, please send them to &email;@FreeBSD.org.

  11. How can I control what fonts are anti-aliased?

    GNOME &gnomever; makes use of libXft and fontconfig to handle anti-aliasing. Fontconfig is a very powerful XML-based font configuration package. You can create a ~/.fonts.conf file that controls virtually every aspect of fontconfig. For example, if you do not want to anti-alias fonts smaller than 16 point, create a ~/.fonts.conf with the following contents:

     <?xml version="1.0"?>
 <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
 <fontconfig>
 
 <match target="font">
         <test name="size" compare="less_eq">
                 <double>16</double>
         </test>
         <edit name="antialias" mode="assign">
                 <bool>false</bool>
         </edit>
 </match>
 <match target="font">
         <test name="pixelsize" compare="less_eq">
                 <double>16</double>
         </test>
         <edit name="antialias" mode="assign">
                 <bool>false</bool>
         </edit>
 </match>
 </fontconfig>

    Refer to fonts-conf(5) for more information.

  12. How do I edit my GNOME 2 menus?

    Right-click on the Applications menu, and select Edit Menus. This will invoke the alacarte menu editing tool.

  13. How do I use GTK+ 2 resource settings for GTK+ 2 applications when not in a GNOME environment?

    GNOME 2 applications get their GTK+ 2 resources from themes and the corresponding theme engine. If you would rather run your GTK+ 2 applications in a non-GNOME environment then you will need to create a file named ~/.gtkrc-2.0.

    To use the widgets from a GTK+ 2 theme when in a non-GNOME environment, simply include the theme's gtk-2.0/gtkrc in your ~/.gtkrc-2.0. For example: 

    include "/usr/local/share/themes/Crux/gtk-2.0/gtkrc"

    If you prefer, you can use the same GTK+ 1.2 theme for both GTK+ 1.2 and GTK+ 2 applications, which will give your GTK+ programs a consistent look. For the most part, you can transfer your settings from your ~/.gtkrc file (used for GTK+ 1.2) with a couple of caveats.

    1. If you have any theme engine references, you will have to make sure there is a corresponding GTK+ 2 theme engine. Otherwise, remove the engine entries.
    2. The default font specification should be outside of any style blocks and should be specified with the gtk-font-name keyword. For example: 
      gtk-font-name = "Verdana 11"

    Note that while a GTK+ 1.2 gtkrc file will work in a GTK+ 2 gtkrc-2.0 file, the opposite is not true: the contents of a GTK+ 2 gtkrc-2.0 file will not work inside a GTK+ 1.2 gtkrc file.

    For simply switching GTK+ themes without needing to edit your ~/.gtkrc files, you can use the x11/gtk-theme-switch and x11/gtk2-theme-switch ports.

  14. How do I configure settings for GNOME 1.4 applications under GNOME &gnomever;?

    Install sysutils/gnome-control-center1, then invoke gnomecc from the command line to bring up the GNOME 1.4 control center.

  15. Nautilus-cd-burner does not let me burn CDs or Totem/Goobox/Sound-juicer cannot find my CD/DVD drive. How can I fix this?

    Nautilus-cd-burner, totem, goobox, and sound-juicer cannot use CD/DVD drives unless support for those devices is enabled in the kernel, and the permissions on the device nodes allow write access. Nautilus-cd-burner, totem, goobox, and sound-juicer talk to CD/DVD drives through the SCSI CAM subsystem. Therefore, you must make sure you have the following configured in your kernel:

     device          scbus
 device          cd
 device          pass

    You must also make sure you have the following configured in your kernel if you are using an ATAPI CD/DVD drive:

     device		atapicam

    Finally, if you are running GNOME 2.16 or later, you must have HAL running, or you will only be able to burn to an ISO image file.

    To figure out which CD/DVD drive you will be using, run the following command as root:

     # camcontrol devlist

    Your output will look similar to the following:

     <QSI CDRW/DVD SBW-242 UD22>		at scbus1 target 0 lun 0 (cd0,pass0)

    The devices in parentheses at the end are important. You must make sure the /dev entries for those devices are writable by the users that will be using nautilus-cd-burner, totem, goobox, or sound-juicer. In addition to those devices, /dev/xpt* must also be writable to your nautilus-cd-burner, totem, goobox, and sound-juicer users. The following /etc/devfs.conf configuration will achieve the desired results given the above devlist:

     perm    cd0     0666
 perm    xpt0    0666
 perm    pass0   0666

    If you encounter problems burning to discs with nautilus-cd-burner, set the following GConf /apps/nautilus-cd-burner/debug to true using Applications > System Tools > Configuration Editor (gconf-editor from the command line). Then run nautilus-cd-burner from the command line, reproduce the problem you are having, and capture the output on the command line. Include this along with the rest of your bug report.

  16. How do I add new GDM sessions?

    The process for adding new GDM sessions has changed substantially between GNOME 2.2 and &gnomever;. In order to add new sessions now, you must create a .desktop file containing the session configuration information. Session files live in /usr/local/etc/dm/Sessions. For example, to add a KDE session, create a file in /usr/local/etc/dm/Sessions called kde.desktop. That file should contain the following:

     [Desktop Entry]
 Encoding=UTF-8
 Name=KDE
 Comment=This session logs you into KDE
 Exec=/usr/local/bin/startkde
 TryExec=/usr/local/bin/startkde
 Icon=
 Type=Application

    This file must have execute permissions. For example:

     # chmod 0555 kde.desktop

    After creating this file, restart GDM, and there will be a KDE link under the Sessions menu.

  17. How do I disable spatial Nautilus?

    As of GNOME 2.8, Nautilus operates in what is known as a "spatial" mode. This means that each item is opened in a new window. This may not be desirable to all users. If you wish to revert back to the old Nautilus file system browser, go to Desktop->Preferences->File Management, click on the Behavior tab, and check the "Always open in browser windows" checkbox.

  18. How do I disable desktop icons for "Computer," "Home," and "Trash?"

    If you do not want your desktop cluttered with the default icons for "Computer," "Home," and "Trash," you can disable any or all of them. To do this, launch Applications > System Tools > Configuration Editor (gconf-editor from the command line), and go to the /apps/nautilus/desktop key. From here, you can enable or disable the icons, and even rename "Home" and "Trash."

  19. How do I mount my removable media in Nautilus?

    As of GNOME 2.16, FreeBSD supports HAL, a component from the FreeDesktop project. HAL provides seamless hardware integration with modern UNIX desktop environment such as GNOME. This means auto-mounting of hardware is as easy as starting a few daemons at boot time, and making sure sysutils/gnome-volume-manager is installed. If you installed x11/gnome2 you already have gnome-volume-manager installed.

    The daemons that must be started prior to logging into GNOME are, dbus, polkitd, and hald in that order. To do this, add the following to /etc/rc.conf, and reboot:

     dbus_enable="YES"
 polkitd_enable="YES"
 hald_enable="YES"

    These services are automatically started if all GNOME features are enabled.

    Note: your user account must be a member of the operator group for automatic mounting to work. To add yourself to the operator group, execute the following command as root:

     # pw group mod operator -m <username>

    For example, to add the user marcus to the operator group, use the following command:

     # pw group mod operator -m marcus

    That's it! You should now see your USB key drives and CD-ROMs magically appear on your desktop. However, if you are having problems with auto-mounting or HAL in general, you should collect the following (in addition to other troubleshooting information):

    1. Output of lshal
    2. Output of sysctl -b kern.geom.conftxt
    3. Contents of /etc/fstab
    4. Output of mount
    5. Full dmesg output
    6. Stop hald, then run it manually using /usr/local/sbin/hald --daemon=no --verbose-yes and provide the output
    7. If using GNOME, and a volume is not mounting properly, include the output of gnome-mount --block --no-ui --verbose --hal-udi <Device UDI> (<Device UDI> is the Unique Device Identifier obtained from the output of lshal for the device that is not mounting properly)

    You can also mount fixed storage media such as FAT or NTFS partitions (maybe you are dual booting) using HAL. For this to work you must must edit /usr/local/etc/PolicyKit/privilege.d/hal-storage-fixed-mount.privilege and add your username to the Allow list:

     [Policy]
 Allow=uid:<username>

    For example, to allow the user marcus to mount fixed storage media, add the following to hal-storage-fixed-mount.privilege:

     [Policy]
 Allow=uid:marcus

    Gary Dunn also provides a very detailed how-to for user-mounting SMB volumes.

  20. Why is GNOME so slow to start up?

    Under normal circumstances, GNOME should only take a few seconds to start up (fifteen at most). However, certain configurations may cause it to hang for up to an hour at login time.

    First, make sure your machine's hostname properly resolves. To test this, run the following command:

     ping `hostname`

    If the command fails, you will either have to add your fully-qualified hostname to DNS or to /etc/hosts. If you do not have a static IP address, you can append your hostname to the localhost line in /etc/hosts. For example, if your machine's hostname is gnome-rocks.mydomain.com, edit /etc/hosts, and change the line:

     127.0.0.1               localhost localhost.my.domain

    To:

     127.0.0.1              localhost localhost.my.domain gnome-rocks gnome-rocks.mydomain.com

    Finally, if you have either the TCP or UDP blackhole sysctl enabled, this may cause GNOME to stall on login. If, after fixing hostname resolution, GNOME still takes a long time to startup, verify the following sysctls are set to 0:

     net.inet.tcp.blackhole
 net.inet.udp.blackhole

  21. How do I install GNOME packages from the GNOME Tinderbox?

    The GNOME Tinderbox is a service that continually builds i386 and amd64 packages of the GNOME desktop for all supported versions of FreeBSD. As hardware gets better, more meta-ports may be added in the future. This service can be a great way of getting the latest GNOME desktop without having to wait for everything to build from ports.

    To install packages from the GNOME Tinderbox, you must set the PACKAGESITE environment variable to the correct package directory. The package directory can be found by clicking on the Package Directory link on the main Tinderbox page for your architecture. Once you have the correct package directory, you should append /Latest/ to it so you can pkg_add gnome2 without knowing any additional version numbers. For example, if you are installing on i386 FreeBSD 6.1, set PACKAGESITE to the following:

     http://www.marcuscom.com/tb/packages/6.1-FreeBSD/Latest/

    If you are installing on amd64 FreeBSD 6.1, set PACKAGESITE to the following:

     http://www.marcuscom.com/tb/packages-amd64/6.1-FreeBSD/Latest/

  22. How do I add new MIME types to GNOME?

    Since GNOME 2.8, MIME types are stored in the new FreeDesktop shared-mime-info database. However, gnome-control-center has not been updated to allow one to easily add MIME types to this database. Therefore, if applications such as Nautilus complain that there is no MIME type associated with a particular file, using the Open With tab under Properties not work.

    New MIME types can be added in one of two places. They can either be added system-wide for all users, or added locally on a per-user basis. System-wide MIME types must be added to LOCALBASE/share/mime , where as local MIME types must be added to ~/.local/share/mime. In both cases, the procedure is the same.

    To define a new MIME type, you must create an application and a packages file to describe it. The application file will be named for the MIME type, and contain its name and a brief comment describing it. The packages file will list all the extensions associated with this MIME type as well as any special file magic that can be used to identify files without an extension.

    For example, if we wanted to add a new local MIME type for Windows HTML Help files (i.e. .chm files) called application/x-chm, we would do the following. First, we would create the directories ~/.local/share/mime/application and ~/.local/share/mime/packages if they did not already exist. Then, we create an application file called x-chm.xml that we will place in ~/.local/share/mime/application. The file looks like:

     <?xml version="1.0" encoding="UTF-8"?>
 <mime-type
 xmlns="http://www.freedesktop.org/standards/shared-mime-info"
 type="application/x-chm">
   <comment>Windows HTML Help file</comment>
 </mime-type>

    Next, we create a packages file called chm.xml that we will place in ~/.local/share/mime/packages. The file looks like:

     <?xml version="1.0" encoding="UTF-8"?>
 <mime-info
 xmlns="http://www.freedesktop.org/standards/shared-mime-info">
   <mime-type type="application/x-chm">
     <comment>Windows HTML Help file</comment>
     <glob pattern="*.chm" />
   </mime-type>
 </mime-info>

    Once the files have been created, the MIME database must be updated. To do that, run the command:

     % update-mime-database ~/.local/share/mime

    Finally (and unfortunately), you must logout and log back in to GNOME for the changes to fully take effect. Nautilus' Properties->Open With interface can now be used to associate an application to this MIME type. Hopefully all of this will be made much easier in a future GNOME release.

  23. How do I configure GDM for automatic logins?

    The GNOME Display Manager (GDM) can be configured to automatically log a user in when it starts up. To do that, you must first configure Pluggable Authentication Module (PAM) support for gdm-autologin. Create a /etc/pam.d/gdm-autologin file with the following contents:

     auth       required     pam_nologin.so
 auth       required     pam_permit.so
 account    required     pam_unix.so
 session    required     pam_permit.so

    Once PAM is configured to allow GDM automatic logins, edit /usr/local/etc/gdm/custom.conf, and set AutomaticLoginEnable=true, and AutomaticLogin equal to the username for which you wish to enable automatic logins. Both of these properties should be placed under the [security] heading. For example:

     [security]
 AutomaticLoginEnable=true
 AutomaticLogin=marcus

    That will automatically login the user marcus as soon as GDM launches.

  24. How do I upgrade from gnome2-lite to the full GNOME &gnomever; desktop?

    The Lite edition does not include all of the components of the standard GNOME &gnomever; desktop. If you wish to install the full desktop, first remove the gnome2-lite package, then install the gnome2 port or package. For example:

     # pkg_delete gnome2-lite

    Then one of the following:

     # cd /usr/ports/x11/gnome2
 # make install clean

    or:

     # pkg_add -r gnome2

    Alternatively, you can install additional GNOME components individually using either their ports or packages.

  25. How do I enable Emacs-style keybindings in GTK+ applications?

    By default, GTK+ uses Windows-like keyboard shortcuts for command line editing. Many UNIX users are more familiar or more comfortable with Emacs-style shortcuts. For example, GTK+ uses Control+A to mean, "select all," where as Emacs uses Control+A to mean, "put cursor at the beginning of line."

    In order to use Emacs-style keybindings in GTK+ applications, edit ~/.gtkrc-2.0, and add the following:

     gtk-key-theme-name = "Emacs"

    If you are using the GNOME Desktop, however, this is not sufficient. You must also change the GConf key /desktop/gnome/interface/gtk_key_theme to "Emacs" using Applications > System Tools > Configuration Editor (gconf-editor from the command line).

  26. Why do I only see generic icons in Nautilus?

    This typically occurs for users that are not running the full GNOME Desktop. By default, gnome-session will start gnome-settings-daemon automatically. This daemon is responsible for setting many GTK+ and GNOME preferences including the icon theme. If you are not running the GNOME Desktop, make sure the following has been added to your X11 session startup preferences:

     /usr/local/libexec/gnome-settings-daemon &

    If you are running the full GNOME Desktop, there may be a problem executing gnome-settings-daemon. Try running /usr/local/libexec/gnome-settings-daemon from the command line, and check for any errors. Most problems can be solved by reinstalling sysutils/gnome-control-center.

  27. Why do I need confirm access to my keyring every time Nautilus tries to open an external share?

    You did not mount the procfs file system. Which is off by default in recent releases of FreeBSD. Consider adding the following line to your /etc/fstab file:

     proc			/proc		procfs	rw	0	0
&footer; diff --git a/en/gnome/docs/gnome1_porting.sgml b/en/gnome/docs/gnome1_porting.sgml index 31e22309dc..b0f7107baf 100644 --- a/en/gnome/docs/gnome1_porting.sgml +++ b/en/gnome/docs/gnome1_porting.sgml @@ -1,171 +1,172 @@ - + + ]> &header;

To see how to utilize these components, please examine the example Makefile.

COMPONENT ASSOCIATED PROGRAM IMPLIED COMPONENTS
bonobo devel/bonobo oaf gnomeprint
gal x11-toolkits/gal libglade
gconf devel/gconf oaf
gdkpixbuf graphics/gdk-pixbuf gtk12
glib12 devel/glib12 pkgconfig
glibwww www/glibwww gnomelibs
gnomecanvas graphics/gnomecanvas gnomelibs gdkpixbuf
gnomedb databases/gnome-db libgda
gnomelibs x11/gnome-libs esound imlib libxml orbit
gnomeprint print/gnome-print gnomelibs gnomecanvas
gnomevfs devel/gnome-vfs1 gnomemimedata gconf gnomelibs
gtk12 x11-toolkits/gtk12 glib12
gtkhtml www/gtkhtml glibwww gal libghttp libcapplet
imlib graphics/imlib gtk12
libcapplet x11/libcapplet gnomelibs
libgda databases/libgda gconf bonobo
libghttp www/libghttp  
libglade devel/libglade gnomedb
libxml textproc/libxml glib12
oaf devel/oaf orbit libxml
orbit devel/ORBit glib12
pygnome x11-toolkits/py-gnome gtkhtml pygtk
pygtk x11-toolkits/py-gtk gnomelibs gdkpixbuf libglade

If you still need help with your port, have a look at some of the existing ports for examples. The freebsd-gnome mailing list is also there for you.

&footer; diff --git a/en/gnome/docs/gnome2_porting.sgml b/en/gnome/docs/gnome2_porting.sgml index 2f4e07495b..4fc79ada1b 100644 --- a/en/gnome/docs/gnome2_porting.sgml +++ b/en/gnome/docs/gnome2_porting.sgml @@ -1,353 +1,354 @@ - + + ]> &header;

To see how to utilize these components, please examine the example Makefile.

COMPONENT ASSOCIATED PROGRAM IMPLIED COMPONENTS
atk accessibility/atk glib20
atspi accessibility/at-spi gail libbonobo
desktopfileutils devel/desktop-file-utils glib20
eel2 x11-toolkits/eel gnomemenus gnomedesktop gail
evolutiondataserver databases/evolution-data-server libgnome
gail accessibility/gail libgnomecanvas
gal2 x11-toolkits/gal2 gnomeui libgnomeprintui
gconf2 devel/gconf2 orbit2 libxml2 gtk20 linc
glib20 devel/glib20 gnometarget pkgconfig
gnomecontrolcenter2 sysutils/gnome-control-center gnomedesktop metacity nautilus2 gnomemenus desktopfileutils libgnomekbd gnomepanel
gnomedesktop x11/gnome-desktop libgnomeui gnomedocutils
gnomedocutils textproc/gnome-doc-utils libxslt
gnomemenus x11/gnome-menus gnomevfs2
gnomepanel x11/gnome-panel gnomedesktop libwnck
gnomespeech accessibility/gnome-speech libbonobo
gnomevfs2 devel/gnome-vfs gconf2 libbonobo gnomemimedata
gtk20 x11-toolkits/gtk20 intltool atk pango
gtkhtml3 www/gtkhtml3 gail libgnomeui libgnomeprintui
gtksourceview x11-toolkits/gtksourceview libgnome libgnomeprintui
libartlgpl2 graphics/libart_lgpl pkgconfig
libbonobo devel/libbonobo libxml2 orbit2
libbonoboui x11-toolkits/libbonoboui libgnomecanvas libgnome
libgailgnome x11-toolkits/libgail-gnome libgnomeui atspi
libgda2 databases/libgda2 glib20 libxslt
libgda3 databases/libgda3 glib20 libxslt
libglade2 devel/libglade2 libxml2 gtk20
libgnome x11/libgnome libxslt gnomevfs2 esound
libgnomecanvas graphics/libgnomecanvas libglade2 libartlgpl2
libgnomedb databases/libgnomedb libgnomeui libgda3
libgnomekbd x11/libgnomekbd libgnomeui
libgnomeprint print/libgnomeprint libbonobo libartlgpl2 gtk20
libgnomeprintui x11-toolkits/libgnomeprintui libgnomeprint libgnomecanvas
libgnomeui x11-toolkits/libgnomeui libbonoboui
libgsf devel/libgsf gconf2 glib20 libxml2
libgsf_gnome devel/libgsf-gnome libgsf gnomevfs2
libgtkhtml www/libgtkhtml libxslt gnomevfs2 gail
libidl devel/libIDL glib20
librsvg2 graphics/librsvg2 libgsf gtk20
libwnck x11-toolkits/libwnck gtk20
libxml2 textproc/libxml2 pkgconfig
libxslt textproc/libxslt libxml2
libzvt x11-toolkits/libzvt gtk20
linc net/linc glib20
metacity x11-wm/metacity gconf2 glade2
nautilus2 x11-fm/nautilus librsvg2 eel2 gnomedesktop
nautiluscdburner sysutils/nautilus-cd-burner nautilus2 desktopfileutils
orbit2 devel/ORBit2 libidl
pango x11-toolkits/pango glib20
pygnome2 x11-toolkits/py-gnome2 libgnomeui pygtk2
pygnomedesktop x11-toolkits/py-gnome-desktop pygnome2 libgnomeprintui gtksourceview libwnck nautiluscdburner
pygnomeextras x11-toolkits/py-gnome-extras pygnome2 libgtkhtml
pygtk2 x11-toolkits/py-gtk2 libglade2
vte x11-toolkits/vte gtk20

If you still need help with your port, have a look at some of the existing ports for examples. The freebsd-gnome mailing list is also there for you.

&footer; diff --git a/en/gnome/docs/gnome_porting.sgml b/en/gnome/docs/gnome_porting.sgml index abce3be7b4..2d1ab0e00c 100644 --- a/en/gnome/docs/gnome_porting.sgml +++ b/en/gnome/docs/gnome_porting.sgml @@ -1,149 +1,150 @@ - + + ]> &header;

To see how to utilize these components, please examine the example Makefile.

COMPONENT ASSOCIATED PROGRAM IMPLIED COMPONENTS
esound audio/esound  
gnomehack gnomehack makes common GNOME Makefile substitutions that nearly every GNOME port requires to fit into the proper mtree structure.
gnomehier gnomehier installs all the directories needed for both the GNOME 1 and 2 desktops. Only include this option if your port calls @dirrm on one of the directories listed in the plist for gnomehier.
gnomemimedata misc/gnome-mime-data gnomehier pkgconfig
gnomeprefix gnomeprefix sets some CONFIGURE_ARGS to ensure data is placed properly within the GNOME hierarchy. gnomehier
gnometarget gnometarget sets ${CONFIGURE_TARGET} for ports whose configure script does not figure it out automatically.  
intlhack intlhack registers a dependency upon textproc/intltool and patches broken intltool-merge.in implementations. intltool
intltool intltool registers a BUILD_DEPENDS on textproc/intltool.  
lthack lthack prevents the installation of .la files and ensures that ${PTHREAD_LIBS} will be passed to the linker. NOTE: lthack is DEPRECATED, and USE_AUTOTOOLS=libtool:15 should be used instead. See the libtool section of the porting guide for more details.  
ltverhack ltverhack noralizes shared object versions so that they do not change needlessly. Using ltverhack keeps shared object versions in line with what they should be and what they end up being on other operating systems. In order to use ltverhack the port must define USE_AUTOTOOLS=libtool:15.  
pkgconfig pkgconfig registers a dependency upon devel/pkg-config to make sure it is installed.  
referencehack referencehack is designed for ports that install API reference documentation. These ports should use referencehack then another port with a -reference suffix should be created to install this documentation. See devel/glib20 and devel/glib20-reference for an example.  

If you still need help with your port, have a look at some of the existing ports for examples. The freebsd-gnome mailing list is also there for you.

&footer; diff --git a/en/gnome/docs/porting.sgml b/en/gnome/docs/porting.sgml index fa865edd3b..60867eb828 100644 --- a/en/gnome/docs/porting.sgml +++ b/en/gnome/docs/porting.sgml @@ -1,382 +1,383 @@ - + + ]> &header;

This document assumes that you already know how the port system works, and therefore only provides GNOME-specific hints and tips. General instructions can be found in the FreeBSD Porter's Handbook.

Example Makefile

There is an example Makefile for a GNOME port, which uses many of the tricks outlined in this document. Please feel free to use it as a guide for creating your own ports.

GNOME Makefile Macros

GNOME applications under FreeBSD use the USE_GNOME infrastructure. To specify which components of the GNOME system your port needs in order to build, simply list them all as a space-separated list. For example:

 USE_XLIB=	yes
 USE_GNOME=	gnomeprefix gnomehack libgnomeui

The USE_GNOME components are divided into the following two lists:

If your port needs only GTK2 libraries, the following is the shortest way to define this:

 USE_XLIB=	yes
 USE_GNOME=	gtk20

If your port needs only GTK1 libraries, the following is the shortest way to define this:

 USE_XLIB=	yes
 USE_GNOME=	gtk12

Even if your application needs only the GTK libraries, other USE_GNOME components may be useful. Please scan the entire list to make sure your port uses all relevant components.

Once you have finished with your port, it is a good idea to verify that your port depends on the correct list of components. To see a list of what packages your port will actually require, use the command make package-depends from within your port's directory.

To aid in creating the list of necessary components, it can be helpful to examine the output of make configure. At the end of the checking for... list, there will be a line similar to this:

 checking for	libgnomeui-2.0 >= 2.0.0		cspi-1.0 >= 1.1.7
 libspi-1.0 >= 1.1.7		libbonobo-2.0 >= 2.0.0	atk >= 1.0.0
 gtk+-2.0 >= 2.0.0	gail	libwnck-1.0		esound... yes

This is a list of the components upon which this application relies to build. Pay close attention to the hierarchical layout of the USE_GNOME system; many components are implied from other USE_GNOME directives. In the above example, USE_GNOME= libgnomeui implies use of libbonoboui, which implies libgnomecanvas, which implies libglade2, which implies gtk20. Thus, even though gtk+-2.0 appears in the list of requisite components, gtk20 can be eliminated from the USE_GNOME list. There are a number of other such redundancies that can be eliminated from this list.

For the above list (taken from sysutils/gok), the following is defined in the Makefile: 

 USE_GNOME=	gnomehack gnomeprefix libgnomeui atspi libwnck

GNOME 1 Desktop vs. GNOME 2 Desktop

In the beginning, there was only GNOME 1. When the GNOME 2 desktop came around, maximum backwards compatibility was ensured, within reason. GNOME 1 applications can run fine under the GNOME 2 desktop, provided that the applications do not utilize functionality specific to the GNOME 1 desktop environment.

The GNOME 1 desktop, and all applications that will not run under the GNOME 2 desktop, have been removed from the ports tree.

What this means for you, as an application porter, is simply that you should not add GNOME 1-specific applications to the ports tree.

If you wish to determine which version of the GNOME desktop environment is present on a user's machine, you can check the value of GNOME_DESKTOP_VERSION. This variable is set to either "1" or "2" depending upon whether the GNOME 1 or GNOME 2 desktop is installed.

Optional GNOME Dependencies

If your port can optionally use GNOME, you must set WANT_GNOME= yes in your Makefile, then check to see if HAVE_GNOME is set for each component from the list above that your port can use. Since this is a conditional evaluation, you need to stick it between bsd.port.pre.mk and bsd.port.post.mk. For example:

 WANT_GNOME=	yes
 
 .include <bsd.port.pre.mk>
 
 .if ${HAVE_GNOME:Mgnomepanel}!=""
 	USE_GNOME+=	gnomeprefix gnomepanel
 	CONFIGURE_ARGS+=	--with-gnome
 	PKGNAMESUFFIX=	-gnome
 	PLIST_SUB=	DATADIR="share/gnome"
 .else
 	CONFIGURE_ARGS+=	--without-gnome
 	PLIST_SUB=	DATADIR="share"
 .endif
 
 .include <bsd.port.post.mk>

Here, WANT_GNOME tells the ports system to check for the existence of the various GNOME components listed above. For each component found, its name is appended to HAVE_GNOME. Since this port can use gnomepanel, we check HAVE_GNOME to see if it contains gnomepanel (for more on the :Mpattern make syntax, please refer to the make(1) manpage). If gnomepanel is found, then it is added the list of USE_GNOME dependencies, and the port-specific --with-gnome CONFIGURE_ARG is passed. In an old GNOME infrastructure, PKGNAMESUFFIX was automatically adjusted by the proper USE_* macro. Now it is up to the individual porter to do this. Our example port appends -gnome to the port name to indicate it has been built with GNOME support. The same is true for the DATADIR PLIST_SUB. The individual porter must decide when do the DATADIR substitution. A good rule of thumb is to add the DATADIR PLIST_SUB when using the gnomeprefix component.

Note: You cannot add extra default USE_GNOME components after the .include <bsd.port.pre.mk>. That is, the following is wrong :

 .include <bsd.port.pre.mk>
 
 .if ${HAVE_GNOME:Mgnomelibs}!=""
 	USE_GNOME+=	libgnome
 .else
 	USE_GNOME+=	gtk12  # WRONG!
 .endif

This will make the build system think that GNOME is desired, and mark the pkg-plist accordingly, thus breaking package builds. If you need to add default USE_GNOME components, do so above the .include <bsd.port.pre.mk> line.

To enforce use of optional GNOME dependencies unconditionally, you can add WITH_GNOME= yes to /etc/make.conf or on the make command line. This will always return true when checking for optional GNOME dependencies. If you want the system to always return false when checking for optional GNOME dependencies, you can add WITHOUT_GNOME= yes to /etc/make.conf or to the make command line.

More information on the USE_GNOME infrastructure can be found by looking at the source and comments of ${PORTSDIR}/Mk/bsd.gnome.mk.

GNOME PREFIX

Since the release of 2.16, GNOME now lives in LOCALBASE instead of X11BASE. To make it easier for GNOME ports that must also be installed into the same PREFIX as GNOME, a hack has been added to bsd.gnome.mk to force the PREFIX to LOCALBASE whenever the gnomeprefix component is used. This can be overridden by manually specifying PREFIX in your port's Makefile or on the command line.

OMF Installation

A large number of GNOME applications (especially GNOME 2 applications) install Open Source Metadata Framework (OMF) files which contain the help file information for those applications. These OMF files require special processing by ScrollKeeper in order for applications like Yelp to find help documentation. In order to accomplish proper registry of these OMF files when installing GNOME applications from packages, you should make sure that omf files are listed in pkg-plist and that your Makefile has this defined:

 INSTALLS_OMF=yes

GConf Schema Installation

GConf is the XML-based database that virtually all GNOME applications use for storing their settings. This database is defined by installed schema files that are used to generate %gconf.xml key files. Previously, these schema files and %gconf.xml key files were listed in the port's pkg-plist. Since this proved to be problematic, handling of GConf schemas was changed to something similar to that of MANn files. That is, for each schema file installed by your port, you must have the following listed in the Makefile:

 GCONF_SCHEMAS=	my_app.schemas my_app2.schemas my_app3.schemas

For example in audio/gnome-media:

 GCONF_SCHEMAS=	CDDB-Slave2.schemas gnome-audio-profiles.schemas \
 		gnome-cd.schemas gnome-sound-recorder.schemas

The schema files and %gconf.xml key files should not be in the pkg-plist. If you notice that the port doesn't has any %gconf.xml key files, but has schema files then you should not be use GCONF_SCHEMAS. It means, this port has broke either schema files or installation of GConf.

Shared MIME database

If your port install files like application/x-portname.xml in share/mime, you have to add these two lines at the end of the pkg-plist:

 @exec %%LOCALBASE%%/bin/update-mime-database %D/share/mime
 @unexec %%LOCALBASE%%/bin/update-mime-database %D/share/mime

Also make sure shared-mime-info is among the dependencies of your port. If your port use gtk20, you will have shared-mime-info indirectly. You can check indirect dependencies with make describe.

Example port to look at: deskutils/drivel

Desktop database

Some ports provide MIME definitions in their .desktop files. If your port install .desktop file into share/gnome/applications and there is a line starting with MimeType in it, you need to update desktop database after install and deinstall. This database is represented by share/gnome/applications/mimeinfo.cache file. Add dependency on GNOME component desktopfileutils and these lines to the end of pkg-plist:

 @exec %%LOCALBASE%%/bin/update-desktop-database > /dev/null || /usr/bin/true
 @unexec %%LOCALBASE%%/bin/update-desktop-database > /dev/null || /usr/bin/true

Also add following to the post-install target in port's Makefile:

 -@update-desktop-database

Example port to look at: editors/leafpad

Libtool Issues

Most, if not all, GNOME applications depend on GNU's libtool. They also use the GNU configure system. If your port installs shared libraries, and includes an ltmain.sh script in its ${WRKSRC} directory, you should add USE_AUTOTOOLS=libtool:15 to your port's Makefile. However, if your port uses custom LIBTOOLFLAGS, you must use USE_AUTOTOOLS=libtool:13:inc instead. If you have to use libtool:X:inc, you must also add lthack to USE_GNOME. In general, though, lthack is deprecated, and should only be used if absolutely necessary.

Distfiles

To separate GNOME 2 distfiles from the GNOME 1 distfiles, and to keep the distfiles directory clean, GNOME 1 ports that download their distfiles from ${MASTER_SITE_GNOME} must add the following to their Makefile:

 DIST_SUBDIR=    gnome

GNOME 2 ports that download their distfiles from ${MASTER_SITE_GNOME} must include the following in their Makefile:

 DIST_SUBDIR=    gnome2

Some GNOME distfiles come in both tar gzip as well as tar bzip2 format. To save time when downloading distfiles over slow links, you should use the bzip2 distfiles whenever possible. To do this, add the following to your port's Makefile:

 USE_BZIP2=  yes

If you still need help with your port, have a look at some of the existing ports for examples. The freebsd-gnome mailing list is also there for you.

&footer; diff --git a/en/gnome/docs/volunteer.sgml b/en/gnome/docs/volunteer.sgml index c948205441..8bec50efdc 100644 --- a/en/gnome/docs/volunteer.sgml +++ b/en/gnome/docs/volunteer.sgml @@ -1,46 +1,47 @@ - + + ]> &header;

There is always something to do around the GNOME FreeBSD camp. Grab something that sounds interesting to you, and run with it.

Send any feedback to &email;@FreeBSD.org.

&footer;