Hi there Christian, Gaute, people on the GNOME l18n list and Fedories on
the Fedora Config list!
http://cvs.gnome.org/viewcvs/gnome-schedule/
On Thu, 2004-06-17 at 23:10 +0200, Christian Rose wrote:
> There's even more problems with gnome-schedule in its current state.
>
> One of the most important ones is that it doesn't work with
> intltool-update.
I have fixed this build environment. It's now using autoconf and
automake for it's deployment and building steps.
Checkout the log below to find out where everything is being installed.
If it's your opinion that some files are being deployed at wrong
locations, then please do contact me or fix it in the GNOME CVS after
reading the README.cvs or HACKING file.
If translations are impossible cause of this build environment then you
are free to fix that or to inform me be about the issue. Afaik, however,
I kept as standard/normal-autoconf as possible. Some quirks perhaps to
get the python-scripts installed in $prefix/share/application-name/*py
and to get a little script installed at $prefix/bin/application-name
which will startup the the python-scripts. If such quirks are incorrect,
you are again free to fix it yadi yada..
The Fedora specific scripts, which will for example install the .console
file and the pam settings for gnome-schedule, will be put in the spec
file. If this is not the correct location then please do tell me about
this. I am not going to write the spec file myself because I am probably
the most incapable person to do this :-).
One might want to ask Dag Wieers (http://dag.wieers.com) about how
incapable I am at getting my applications conform to the world of
packagers and their standards, haha -Dag created and hosts packages for
another application of mine, poor guy-. (Dag is in BCC)
Another option would be, I guess, to include a patch that will patch the
sources to prepare it for Fedora Core, just before the src.rpm file will
get compiled. Again I have no idea how to do all this correctly and will
leave it to the professional packagers. As discussed on the Fedora
Config list, we are still committed to getting gnome-schedule included
in Fedora Core as one of it's system-config-* tools (for example the
commandline 'system-config-schedule'). We would prefer this inclusion
not to be a fork of the application. That would only clutter the scene,
right? :). We will, however, not maintain such a fork ourselves.
But .. I would like to stress that gnome-schedule is NOT a Fedora-only
tool! It's purpose it to be a GNOME tool rather than specifically a
Fedora tool. So the Debian, Suse, Ximian, Slackware, Gentoo and
Whateverwere distributions are invited to use gnome-schedule.
[root@elfeling gnome-schedule]# make install
Making install in src
make[1]: Entering directory `/home/freax/cvs/gnome-schedule/src'
make[2]: Entering directory `/home/freax/cvs/gnome-schedule/src'
test -z "/usr/local/bin" || mkdir -p -- . "/usr/local/bin"
/usr/bin/install -c 'gnome-schedule' '/usr/local/bin/gnome-schedule'
test -z "/usr/local/share/gnome-schedule" || mkdir -p -- . "/usr/local/
share/gnome-schedule"
/usr/bin/install -c -m 644 'gnome-schedule.py' '/usr/local/share/gnome-
schedule/gnome-schedule.py'
/usr/bin/install -c -m 644 'config.py' '/usr/local/share/gnome-
schedule/config.py'
/usr/bin/install -c -m 644 'mainWindow.py' '/usr/local/share/gnome-
schedule/mainWindow.py'
/usr/bin/install -c -m 644 'addWindow.py' '/usr/local/share/gnome-
schedule/addWindow.py'
/usr/bin/install -c -m 644 'addWindowHelp.py' '/usr/local/share/gnome-
schedule/addWindowHelp.py'
/usr/bin/install -c -m 644 'setuserWindow.py' '/usr/local/share/gnome-
schedule/setuserWindow.py'
/usr/bin/install -c -m 644 'crontab.py' '/usr/local/share/gnome-
schedule/crontab.py'
Byte-compiling python modules...
gnome-schedule.py config.py mainWindow.py addWindow.py addWindowHelp.py
setuserWindow.py crontab.py
Byte-compiling python modules (optimized versions) ...
gnome-schedule.py config.py mainWindow.py addWindow.py addWindowHelp.py
setuserWindow.py crontab.py
test -z "/usr/local/share/gnome-schedule" || mkdir -p -- . "/usr/local/
share/gnome-schedule"
/usr/bin/install -c -m 644 'gnome-schedule.glade' '/usr/local/share/
gnome-schedule/gnome-schedule.glade'
make[2]: Leaving directory `/home/freax/cvs/gnome-schedule/src'
make[1]: Leaving directory `/home/freax/cvs/gnome-schedule/src'
Making install in pixmaps
make[1]: Entering directory `/home/freax/cvs/gnome-schedule/pixmaps'
make[2]: Entering directory `/home/freax/cvs/gnome-schedule/pixmaps'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/local/share/pixmaps" || mkdir -p -- . "/usr/local/share/
pixmaps"
/usr/bin/install -c -m 644 'gnome-schedule.png' '/usr/local/share/
pixmaps/gnome-schedule.png'
make[2]: Leaving directory `/home/freax/cvs/gnome-schedule/pixmaps'
make[1]: Leaving directory `/home/freax/cvs/gnome-schedule/pixmaps'
Making install in doc
make[1]: Entering directory `/home/freax/cvs/gnome-schedule/doc'
make[2]: Entering directory `/home/freax/cvs/gnome-schedule/doc'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/local/share/doc/gnome-schedule-1.0" || mkdir -p -- . "/
usr/local/share/doc/gnome-schedule-1.0"
/usr/bin/install -c -m 644 'index.html' '/usr/local/share/doc/gnome-
schedule-1.0/index.html'
/usr/bin/install -c -m 644 'addingandediting.html' '/usr/local/share/
doc/gnome-schedule-1.0/addingandediting.html'
make[2]: Leaving directory `/home/freax/cvs/gnome-schedule/doc'
make[1]: Leaving directory `/home/freax/cvs/gnome-schedule/doc'
Making install in po
make[1]: Entering directory `/home/freax/cvs/gnome-schedule/po'
if test -r ".././mkinstalldirs"; then \
.././mkinstalldirs /usr/local/share; \
else \
/bin/sh ../mkinstalldirs /usr/local/share; \
fi
installing sv.gmo as /usr/local/share/locale/sv/LC_MESSAGES/gnome-
schedule.mo
if test "gnome-schedule" = "glib"; then \
if test -r ".././mkinstalldirs"; then \
.././mkinstalldirs /usr/local/share/glib-2.0/gettext/po; \
else \
/bin/sh ../mkinstalldirs /usr/local/share/glib-2.0/gettext/po; \
fi; \
/usr/bin/install -c -m 644 ./Makefile.in.in \
/usr/local/share/glib-2.0/gettext/po/Makefile.in.in; \
else \
: ; \
fi
make[1]: Leaving directory `/home/freax/cvs/gnome-schedule/po'
make[1]: Entering directory `/home/freax/cvs/gnome-schedule'
make[2]: Entering directory `/home/freax/cvs/gnome-schedule'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/freax/cvs/gnome-schedule'
make[1]: Leaving directory `/home/freax/cvs/gnome-schedule'
[root@elfeling gnome-schedule]#
--
Philip Van Hoof, Software Developer @ Cronos
home: me at freax dot org
work: Philip dot VanHoof at cronos dot be
http://www.freax.be, http://www.freax.eu.org
--
Fedora-config-list mailing list
Fedora-config-list@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-config-list
|
