Commit 1ee38db0 authored by Gaute Hope's avatar Gaute Hope

various admin updates

svn path=/trunk/; revision=999
parent 41ccde3f
Hacking on gnome-schedule
-------------------------
Remember to send an email to the gnome-schedule-devel list
or check out the latest code from the subversion repository
in case work has allready been started on some of the features.
Minor changes (build fixes, typos, documentation and small bug fixes)
can be committed at will, but please send a note to the maintainer(s)
alerting them to what you have done and be sure to include a ChangeLog
......
2007-12-02:
Since this file was updated the last time versions: 1.0.0, 1.0.1 and 1.2.0 has been released.
It is time for the (most likely) last release in the 1.x series, there are fairly few updates since the recent 1.2.0 release, but although it was meant as a last translation update I found some significant bugs.
A summary of the Changelog:
∘ Fixed bug in the at editor: choosing dates in the future with a month or day before the current one failed
∘ Fixed some parsing bugs in crontab regarding short term strings in the time expressions (mon, tue, wed)
∘ Fixed some confusing simple expressions regarding weekdays
∘ Removed debug messages
∘ Fixed help open function
∘ Fixed an error in the dialog that pops up if a record is invalid
Other than that it might be worth saying that since this file was updated the last time versions: 1.0.0, 1.0.1 and 1.2.0 has been released.
Other than that it is not much to say about this one. Happy scheduling!
- gaute, 2007-12-02
2006-09-17:
Both at and crontab are using data files in the directory $HOME/.gnome/gnome-schedule/at|crontab
......
......@@ -16,6 +16,7 @@ Dependencies
o. Python
o. PyGTK >= 2.3
o. Python GConf
o. su
Support
-------
......@@ -24,19 +25,19 @@ Support
of gnome-schedule here:
o. http://lists.sourceforge.net/mailman/listinfo/gnome-schedule-users
There is also a development list here:
o. http://lists.sourceforge.net/mailman/listinfo/gnome-schedule-devel
INSTALL from source while PyGTK is not in your default prefix
INSTALL from source:
-------------------------------------------------------------
o. Because some people dislike the fact that manually compiled
applications tamper with their distribution which is managed by the
packaging system in use. We understand this and therefor made it
packaging system in use. We understand this and therefore made it
possible to install the application outside of any default prefix.
o. If you want to use the sources pulled from the subversion server you need automake-1.7 and gnome-common.
o. The following commands will install gnome-schedule on a system that has
Python and automake-1.7 and some tools like gmake installed.
o. The following commands will install gnome-schedule on a system that has python and automake-1.7 and some tools like gmake installed.
$ svn checkout http://svn.gnome.org/svn/gnome-schedule/trunk gnome-schedule
$ pushd gnome-schedule
......@@ -56,11 +57,9 @@ o. The following commands will install gnome-schedule on a system that has
Important notes
---------------
If you have previous records in at, gnome-schedule may have problems reading them.
They are marked as DANGEROUS PARSE in the list if a unsecure method was used. This will not damage
the record, and if you open one pressing cancel in the script editor will not change anything.
If you have previous records in 'at', gnome-schedule may have problems reading them and they are marked with DANGEROUS PARSE in the list if a unsecure method was used. There are no risk that the record will be lost or damaged unless you open it for editing and press apply, but we have tested many different setups and it should work fine.
Some comments right after existing records in crontab may return weird results for title and icon, this should not damage anything.
Some comments right after existing records in crontab may return weird results for title and icon, normally this doesn't damage anything.
Compiling and HACKING
......
TODO
----
Remember to send an email to the gnome-schedule-devel list
or check out the latest code from the subversion repository
in case work has allready been started on some of the features.
Development:
Unassigned unstable (need a new branch and/or will not be
included in the next release)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment