Gnome Process Tree Code
Status: Alpha
Brought to you by:
rockyb
Menu
▾
▴
Tree [fa905d] master / History
rockyb
Read Me
This README document includes:
* General information
* Licensing
* Requirements
* Getting Help & Reporting bugs
=======================
General information
=======================
This directory tree holds the distribution including source code and
documentation for gnopstree, an a program which dynamically displays
via GNOME/GTK+ the Unix processes as a tree or forest, the roots on the
left and the leaf processes (with no children) on the right. The
status of each process running, sleeping, stopped, etc.) can be
indicated by a color.
Of course, the documentation contains more detailed information.
The file NEWS contains a record of user-visible changes.
The file AUTHORS contains a list of the people who have contributed to
this program -- thanks to everyone who has!
The file INSTALL contains the generic installation instructions that
are used by anything build with GNU autoconf.
=============
Licensing
=============
Everything here is released under the terms of the GNU GENERAL PUBLIC
LICENSE (GPL); please read the file COPYING for more information.
===================
Requirements
====================
To run the program at a minimum you need:
- GNOME/GTK 1.2.8 libraries
which implies GNOME is installed. Currently gnopstree runs on a
limited number of Unix platforms like Linux or Solaris. Porting to
other Unix platforms is desirable. Since this program is a
rewrite/port of xps (see http://www.netwinder.org/~rocky/xps-home),
porting to one of the platforms supported by xps should be
straightforward.
To build the program from source you need at a minimum the above and
- A C compiler, preferably gcc since that's what I use
- Usual development tools like Make, preferably GNU make since ...
- Perl (at present) to run the post-configuration script
and to regenerate documentation
=========================
Getting more involved
=========================
If you plan to extend or improve the program or become part of the
maintainer team -- and I encourage you to do so -- you may need a bit
more development tools than what is needed to build source. Additional
tools include:
- autoheader, automake, autoconf
- glade
- possibly CVS and ssh to access, check in/out the source from
the main repository
Get a copy of the source via CVS you need to set the environment variables
CVS_RSH to "ssh" and CVSROOT to
*youraccount*@cvs.gnopstree.sourceforge.net:/cvsroot/gnopstree.
For example in csh/tcsh:
setenv CVS_RSH ssh
setenv CVSROOT joeuser@cvs.gnopstree.sourceforge.net:/cvsroot/gnopstree
and in ksh/bash:
export CVS_RSH=ssh
setenv CVSROOT=joeuser@cvs.gnopstree.sourceforge.net:/cvsroot/gnopstree
assuming you have a "joeuser" login. I have these two statements in a
file that I can use to source inside of a shell. After that you would
cd to the place where you want the code to go and run:
cvs -z3 checkout gnopstree
After checking the repostiory out you will have to run:
aclocal -I macros
autoheader
automake
autoconf
=================================
Getting Help & Reporting Bugs
=================================
There is currently a single mailing list for getting gnopstree help,
reporting problems, making suggestions, discussing code, or submitting
patches, and it is gnopstree-users@lists.sourceforge.net.
Submitting a bug is something very important for developers.
Feedback is useful.
This program is being developed under the kind auspices of sourceforge
and I'm going to try to use its tools -- so please be patient as this
is all new to me too.
Via SourceForge (http://sourceforge.net) you can submit a bug you need
to be logged in. There are instructions on that site for submitting a
bug.
$Id: README,v 1.4 2001/03/14 14:02:39 rockyb Exp $
