scrollkeeper-devel — Developer discussion list for ScrollKeeper

Re: [Scrollkeeper-devel] Scrollkeeper delay

[Dan M. <mu...@al...>]

On 20 Jun 2003, Malcolm Tredinnick wrote:

> On Fri, 2003-06-20 at 21:09, Pablo Fernandez wrote:

> > Is there anyway to avoid the rebuild of the database without rebuilding
> > the packages that use the scrollkeeper-update program?
> 
> Not easily. An ugly, but possibly workable solution would be to
> temporarily alias the scrollkeeper-update name to something harmless
> like ':' and then run scrollkeeper-update once as part of some
> post-install fixup.

Is the system really doing a complete rebuild of the database?  If so, 
then it is duplicating work and it would make sense to have a way to turn 
scrollkeeper off (such as temporarily replacing the binary or having a 
line in /etc/scrollkeeper.conf).  Then when the distribution installation 
is done, you should update the database.

However, when each package installs, it should only be doing an update of 
the database.  Since these are incremental, it shouldn't be much faster to 
do one large update at the end of the distribution installation than to do 
a number of smaller updates during the installation.

If you were in a really big pinch and wanted to hack things, you could 
disable ScrollKeeper during the install and then have a script run later 
(like on the next reboot or off of cron) that restores ScrollKeeper and 
does an update.

The real solution to this problem is to extend ScrollKeeper so that one 
can process the docs at build time and install the generated data so that 
ScrollKeeper doesn't have to do it at install time.  We would need to be 
careful that ScrollKeeper versions are kept track of so that we leave room 
for future extensions without breaking things.  (ie. It checks the version 
number used when generating the files and determines whether they are 
compatible with the installed version of ScrollKeeper.)  This is something 
which definitely needs to be done, although it is a bit of work and has to 
be thought through pretty carefully.  In the end, it will be an optional 
extension, so it won't be too useful until people update their build 
scripts to use it.

-Dan

Re: [Scrollkeeper-devel] Scrollkeeper delay

[Malcolm T. <ma...@co...>]

On Fri, 2003-06-20 at 21:09, Pablo Fernandez wrote:
> I'm a Gnome enthusiastic, I developed Cronos II which is an mail client
> for Gnome.
> 
> I work now at a company that is developing a Linux distribution based on
> KDE and the problem which is the reason I contact you people is that
> none of my coworkers like Gnome and nothing related to it, but I
> insisted too much and they agreed to install Gnome as well. 

Sounds like you have bigger problems, too, since scrollkeeper is
designed to support more than GNOME. Unpleasant. :(

> The problem is that the installation is about 15 minutes longer due to
> scrollkeeper, since it rebuilds it database like five times.

Well, it adds something to the database once for every package with an
OMF file. This problem is _only_ going to bite you on a brand new
install, though, since that is when you are installing a bunch of
packages that use scrollkeeper. There is not really any other way to do
it, either, since there is no way for a package to know if it is being
installed as part of a set or not. Note that exactly the same problem
applies with respect to running, for example, ldconfig when installing
shared libraries. Of course, you don't notice the difference there,
since everything uses shared libraries.

One has to wonder how often your colleagues think people are going to be
installing their machines from scratch. And if the difference is only
fifteen minutes and ... *sigh*. Might as well give up now. :-(

> I been reading the code and I didn't found a way to avoid this, thus why
> I'm writting this. 
> 
> Is there anyway to avoid the rebuild of the database without rebuilding
> the packages that use the scrollkeeper-update program?

Not easily. An ugly, but possibly workable solution would be to
temporarily alias the scrollkeeper-update name to something harmless
like ':' and then run scrollkeeper-update once as part of some
post-install fixup.

Malcolm

[Scrollkeeper-devel] Scrollkeeper delay

[Pablo F. <pa...@bl...>]

Hi

I'm a Gnome enthusiastic, I developed Cronos II which is an mail client
for Gnome.

I work now at a company that is developing a Linux distribution based on
KDE and the problem which is the reason I contact you people is that
none of my coworkers like Gnome and nothing related to it, but I
insisted too much and they agreed to install Gnome as well.=20

The problem is that the installation is about 15 minutes longer due to
scrollkeeper, since it rebuilds it database like five times.

I been reading the code and I didn't found a way to avoid this, thus why
I'm writting this.=20

Is there anyway to avoid the rebuild of the database without rebuilding
the packages that use the scrollkeeper-update program?

I'd really appreciate a responce, since if this doesn't get fix the
solution would probably be to avoid everything of Gnome :(

Thanks,
Pablo Fern=E1ndez.

Re: [Scrollkeeper-devel] libs/scrollkeeper.h.in

[Malcolm T. <ma...@co...>]

On Thu, 2003-06-19 at 16:14, Mariano Suarez-Alvarez wrote:
> Hi all,
> 
> As you probably know, the file src/libs/scrollkeeper.h.in has a couple
> of configuration path automake variables in it (prefix and another one)
> The intent is, clearly, that they be substituted at configure time:
> indeed, the file is listed in the AC_CONFIG_FILES. That does not work...

Yes, you are correct. There are a number of problems like this in the
build of scrollkeeper; one day we should get around to fixing all of
them. This is certainly a good start.

I have a couple of other patches sitting in my scrollkeeper mailbox that
people have sent in, so I will put this with them and put everything
into CVS on the weekend.

Cheers,
Malcolm

[Scrollkeeper-devel] libs/scrollkeeper.h

[Mariano Suarez-A. <al...@ma...>]

Hi all,

As you probably know, the file src/libs/scrollkeeper.h.in has a couple
of configuration path automake variables in it (prefix and another one)
The intent is, clearly, that they be substituted at configure time:
indeed, the file is listed in the AC_CONFIG_FILES. That does not work...

>From the autoconf texinfo doc, one learns that

     Most of these variables have values that rely on `prefix' or
   `exec_prefix'.  It is deliberate that the directory output
   variables keep them unexpanded: typically `@datadir@' will be
   replaced by `${prefix}/share', not `/usr/local/share'.

     This behavior is mandated by the GNU coding standards, [...]

     A corollary is that you should not use these variables except in
   Makefiles. [...]

     Similarly you should not rely on `AC_OUTPUT_FILES' to replace
   `datadir' and friends in your shell scripts and other files, rather
   let `make' manage their replacement.
														    After that, the docs go on to give an example, which, for scrollkeeper, leads easily following
The docs go on to give an example, which is easily adapted to fix the above
scrollkeeper bug. This is not a perfect fix, since BUILT_SOURCES only works
for a few targets, but oh well, most people just make && make install, so
that should be ok.

Follows a patch (which you'll also find as an attachment) to the latest
version I could get my hands on (cvs was down)

Cheers,

	-- m

--- scrollkeeper-0.3.12-orig/configure.in	2003-01-23 03:10:57.000000000 -0300
+++ scrollkeeper-0.3.12/configure.in	2003-06-17 04:43:15.000000000 -0300
@@ -211,7 +211,6 @@

 AC_OUTPUT(
 libs/Makefile
-libs/scrollkeeper.h
 libuuid/Makefile
 cl/Makefile
 cl/src/Makefile
--- scrollkeeper-0.3.12-orig/libs/Makefile.am	2003-01-23 03:10:57.000000000 -0300
+++ scrollkeeper-0.3.12/libs/Makefile.am	2003-06-17 04:43:19.000000000 -0300
@@ -17,5 +17,14 @@
 	database.c \
 	uninstall.c \
 	update-url.c
+
+# Note BUILT_SOURCES is only taken into account for `make all' and `make check'
+# This sucks, but oh well..
+BUILT_SOURCES = scrollkeeper.h

 libscrollkeeper_la_LIBADD = $(XML_LIBS) $(XSLT_LIBS)
+
+scrollkeeper.h : Makefile scrollkeeper.h.in
+	sed -e 's,@localstatedir\@,$(localstatedir),g' \
+	    -e 's,@prefix\@,$(prefix),g' \
+	    scrollkeeper.h.in > scrollkeeper.h



------------------------------------------------------------------------------
Mariano Suárez-Alvarez
Departamento de Matemática
Facultad de Ciencias Exactas y Naturales, Universidad de Buenos Aires
Ciudad Universitaria, Pabellón I. Buenos Aires (1428). Argentina.
http://mate.dm.uba.ar/~aldoc9

   Je pense en effet que, sauf à croire au miracle, on ne peut attendre le
   progrès de la raison que d'une action politique rationnellement orientée
   vers la défense des conditions sociales de l'existence de la raison,
   d'une mobilisation permanente de tous les producteurs culturels en vue
   de défendre, par des interventions continues et modestes, les bases
   institutionnelles de l'activité intellectuelle. Tout projet de
   développement de l'esprit humain qui, oubliant l'enracinement historique
   de la raison, compte sur la seule force de la raison et de la
   prédication rationnelle pour faire avancer les causes de la raison, et
   qui n'en appelle pas à la lutte politique pour tenter de doter la raison
   et la liberté des intruments proprement politiques qui sont les
   conditions de leur réalisation dans l'histoire, reste encore prisonnier
   de l'illusion scolastique.

   Pierre Bourdieu, Le point de vue scolastique, ``Raisons pratiques. 
   Sur la théorie de l'action''. 
   Points, vol. 331. París: Éditions du Seuil, 1994.
------------------------------------------------------------------------------

[Scrollkeeper-devel] libs/scrollkeeper.h.in

[Mariano Suarez-A. <msu...@ar...>]

Hi all,

As you probably know, the file src/libs/scrollkeeper.h.in has a couple
of configuration path automake variables in it (prefix and another one)
The intent is, clearly, that they be substituted at configure time:
indeed, the file is listed in the AC_CONFIG_FILES. That does not work...

From the autoconf texinfo doc, one learns that

     Most of these variables have values that rely on `prefix' or
   `exec_prefix'.  It is deliberate that the directory output
   variables keep them unexpanded: typically `@datadir@' will be
   replaced by `${prefix}/share', not `/usr/local/share'.

     This behavior is mandated by the GNU coding standards, [...]

     A corollary is that you should not use these variables except in
   Makefiles. [...]

     Similarly you should not rely on `AC_OUTPUT_FILES' to replace
   `datadir' and friends in your shell scripts and other files, rather
   let `make' manage their replacement.
														    After that, the docs go on to give an example, which, for scrollkeeper, leads easily following
The docs go on to give an example, which is easily adapted to fix the above
scrollkeeper bug. This is not a perfect fix, since BUILT_SOURCES only works
for a few targets, but oh well, most people just make && make install, so
that should be ok.

Here is a patch (which you'll also find as an attachment) to the latest
version I could get my hands on (cvs was down)

Cheers,

	-- m



--- scrollkeeper-0.3.12-orig/configure.in	2003-01-23 03:10:57.000000000 -0300
+++ scrollkeeper-0.3.12/configure.in	2003-06-17 04:43:15.000000000 -0300
@@ -211,7 +211,6 @@

 AC_OUTPUT(
 libs/Makefile
-libs/scrollkeeper.h
 libuuid/Makefile
 cl/Makefile
 cl/src/Makefile
--- scrollkeeper-0.3.12-orig/libs/Makefile.am	2003-01-23 03:10:57.000000000 -0300
+++ scrollkeeper-0.3.12/libs/Makefile.am	2003-06-17 04:43:19.000000000 -0300
@@ -17,5 +17,14 @@
 	database.c \
 	uninstall.c \
 	update-url.c
+
+# Note BUILT_SOURCES is only taken into account for `make all' and `make check'
+# This sucks, but oh well..
+BUILT_SOURCES = scrollkeeper.h

 libscrollkeeper_la_LIBADD = $(XML_LIBS) $(XSLT_LIBS)
+
+scrollkeeper.h : Makefile scrollkeeper.h.in
+	sed -e 's,@localstatedir\@,$(localstatedir),g' \
+	    -e 's,@prefix\@,$(prefix),g' \
+	    scrollkeeper.h.in > scrollkeeper.h

Re: [Scrollkeeper-devel] API to get the count of newly added omffiles

[Malcolm T. <ma...@co...>]

Hi Raj,

On Tue, 2003-06-17 at 21:55, Rajkumar Sivasamy wrote:
> Am aware that it would need some considerable time to review this patch,
> pls. treat this as a friendly reminder for the same!:)

Nice of you to think that maybe somebody was just taking a long time to
review this rather than thinking it may have just dropped into a black
hole. :-)

I will try to look at this in the next couple of days. The idea looks
correct (although that was clear when you first suggested it), so it
should be just a matter of sorting out any accidental mysteries in the
code.

I'll get back to you shortly.

Cheers,
Malcolm

Re: [Scrollkeeper-devel] API to get the count of newly added omffiles

[Rajkumar S. <raj...@wi...>]

Hi,

Am aware that it would need some considerable time to review this patch,
pls. treat this as a friendly reminder for the same!:)

Thanks,
Raj.



Rajkumar Sivasamy wrote:
> 
> Hi,
> 
> Pls. refer our earlier discussions -
> http://sourceforge.net/mailarchive/forum.php?thread_id=2043389&forum_id=4112.
> 
> I have written the API as proposed and its details are: -
> 
> I. Signature of the API:
> -----------------------
> int scrollkeeper_find_omffile_count (int *install_num, int *upgrade_num,
> int *uninstall_num)
> 
> II. Argument Details:
> --------------------
> install_num - return location for the count of omf files that needs to
> be registered
> upgrade_num - return location for the count of omf files that needs to
> be upgraded
> uninstall_num - return location for the count of omf files that needs to
> be unregistered
> 
> III. Version of scrollkeeper used:
> ---------------------------------
> 0.3.11
> 
> IV. New Files Added:
> -------------------
> a) libs/scrollkeeper-api.h
>    - File to export the API
> 
> b) libs/scrollkeeper-api.c
>    - File to accommodate the API
> 
> c) libs/libscrollkeeper.pc.in
>    - Data for package check macro, it will be used by the applications
> using this API to check for the required version of scrollkeeper
> installed and to link the scrollkeeper lib with the application.
> 
> V. Files Altered:
> ----------------
> a) configure.in
>    - changes for creating the package check file libscrollkeeper.pc from
> libscrollkeeper.pc.in
> 
> b) libs/Makefile.am
>    - changes required for adding new files and installing
> scrollkeeper-api.h in the standard "include directory"
> 
> c) scrollkeeper.h.in
>    - changes to include functions that are used across by
> scrollkeeper-api.c and update.c
> 
> d) cl/src/update.c
>    - export the functions to libs/scrollkeeper-api.c to be in sync with
> the routines declared in scrollkeeper.h
> 
> VI. Implementation and Usage:
> ----------------------------
> The API is written by reusing the existing code for
> 'scrollkeeper-update' (i.e., cl/src/update.c).
> 
> install_num:
> - Say we are installing a new component and its postinstall scripts
> failed to run 'scrollkeeper-update' after installing the omf files in
> standard path. Now, when the user launches the help browser he wouldn't
> be able to view the help for the newly installed component. The help
> browser could make use of "install_num" from the api to check if there
> are any unregistered omf files and if so it can notify the users saying:
> 
> "Unregistered help documents have been detected for some applications.
> Help for these applications will not be available. Please contact your
> system administrator to run 'scrollkeeper-update'."
> 
> uninstall_num:
> - On uninstallation, if a component failed to run 'scrollkeeper-update'
> after removing the <component>.omf file the corresponding link in the
> help browser will be inaccessible and the same can be notified to the
> users in advance by using "uninstall_num" from the API.
> 
> upgrade_num:
> - Say the post install script fails to run 'scrollkeeper-update' after a
> component upgradation and the <identifier url=> in the omf is pointing
> to a new xml file. Since the scrollkeeper_docs/database wasn't updated
> the help browser would still look for the older <>.xml file and will
> fail to show the help. This can be notified to the users by the help
> browser using 'upgrade_num'.
> 
> VII. Attachments:
> ----------------
> a) scrl-patch.diff
>    - Changes for implementing the API in scrollkeeper.
> 
> b) yelp-patch.diff
>    - Patch for gnome help browser as an example for the usage of this
> API.
> 
> Pls. review the patch and give in your valuable comments.
> 
> Thanks & Regards,
> Raj.

Re: [Scrollkeeper-devel] API to get the count of newly added omffiles

[Rajkumar S. <raj...@wi...>]

Hi,

Pls. refer our earlier discussions -
http://sourceforge.net/mailarchive/forum.php?thread_id=2043389&forum_id=4112. 


I have written the API as proposed and its details are: -


I. Signature of the API:
-----------------------
int scrollkeeper_find_omffile_count (int *install_num, int *upgrade_num,
int *uninstall_num)


II. Argument Details:
--------------------
install_num - return location for the count of omf files that needs to
be registered
upgrade_num - return location for the count of omf files that needs to
be upgraded
uninstall_num - return location for the count of omf files that needs to
be unregistered


III. Version of scrollkeeper used:
---------------------------------
0.3.11


IV. New Files Added:
-------------------
a) libs/scrollkeeper-api.h
   - File to export the API

b) libs/scrollkeeper-api.c
   - File to accommodate the API

c) libs/libscrollkeeper.pc.in
   - Data for package check macro, it will be used by the applications
using this API to check for the required version of scrollkeeper
installed and to link the scrollkeeper lib with the application.


V. Files Altered:
----------------
a) configure.in
   - changes for creating the package check file libscrollkeeper.pc from
libscrollkeeper.pc.in

b) libs/Makefile.am
   - changes required for adding new files and installing
scrollkeeper-api.h in the standard "include directory" 

c) scrollkeeper.h.in
   - changes to include functions that are used across by
scrollkeeper-api.c and update.c

d) cl/src/update.c
   - export the functions to libs/scrollkeeper-api.c to be in sync with
the routines declared in scrollkeeper.h


VI. Implementation and Usage:
----------------------------
The API is written by reusing the existing code for
'scrollkeeper-update' (i.e., cl/src/update.c). 

install_num:
- Say we are installing a new component and its postinstall scripts
failed to run 'scrollkeeper-update' after installing the omf files in
standard path. Now, when the user launches the help browser he wouldn't
be able to view the help for the newly installed component. The help
browser could make use of "install_num" from the api to check if there
are any unregistered omf files and if so it can notify the users saying:

"Unregistered help documents have been detected for some applications.
Help for these applications will not be available. Please contact your
system administrator to run 'scrollkeeper-update'."

uninstall_num:
- On uninstallation, if a component failed to run 'scrollkeeper-update'
after removing the <component>.omf file the corresponding link in the
help browser will be inaccessible and the same can be notified to the
users in advance by using "uninstall_num" from the API.

upgrade_num:
- Say the post install script fails to run 'scrollkeeper-update' after a
component upgradation and the <identifier url=> in the omf is pointing
to a new xml file. Since the scrollkeeper_docs/database wasn't updated
the help browser would still look for the older <>.xml file and will
fail to show the help. This can be notified to the users by the help
browser using 'upgrade_num'.


VII. Attachments:
----------------
a) scrl-patch.diff
   - Changes for implementing the API in scrollkeeper.

b) yelp-patch.diff
   - Patch for gnome help browser as an example for the usage of this
API.


Pls. review the patch and give in your valuable comments.

Thanks & Regards,
Raj.

Re: [Scrollkeeper-devel] Gnu Writing Movement

[Gregory L. <gle...@li...>]

On Thu, 2003-05-29 at 22:02, Malcolm Tredinnick wrote:
> On Fri, 2003-05-30 at 14:45, Gregory Leblanc wrote:
> > Hi folks!  I don't know if anybody has seen this, but there is
> > apparently a website[1] for the Gnu Writing Movement, which may or may
> > not be active.  However, I noticed that on one of their webpages[2],
> > that some of their goals could be met nicely with what scrollkeeper
> > provides.  I got an email about the gwm earlier, and I've asked them if
> > they have contact with the folks running the project, but I thought
> > people here might be interested as well.
>=20
> Aah .. the fine art of forgotten footnotes. Indicating to the reader
> that there is more they could know, but you have chosen not to tell
> them. :-)
>=20
> (What are [1] and [2]?)

Bah, that's what I get for writing email while trying to talk on the
phone!

1: http://gwm.gnu.org/
2: http://gwm.gnu.org/article.php?sid=3D6&mode=3Dthreaded&order=3D0  item 2=
b,
in particular

Re: [Scrollkeeper-devel] Gnu Writing Movement

[Malcolm T. <ma...@co...>]

On Fri, 2003-05-30 at 14:45, Gregory Leblanc wrote:
> Hi folks!  I don't know if anybody has seen this, but there is
> apparently a website[1] for the Gnu Writing Movement, which may or may
> not be active.  However, I noticed that on one of their webpages[2],
> that some of their goals could be met nicely with what scrollkeeper
> provides.  I got an email about the gwm earlier, and I've asked them if
> they have contact with the folks running the project, but I thought
> people here might be interested as well.

Aah .. the fine art of forgotten footnotes. Indicating to the reader
that there is more they could know, but you have chosen not to tell
them. :-)

(What are [1] and [2]?)

Malcolm

[Scrollkeeper-devel] Gnu Writing Movement

[Gregory L. <gle...@li...>]

Hi folks!  I don't know if anybody has seen this, but there is
apparently a website[1] for the Gnu Writing Movement, which may or may
not be active.  However, I noticed that on one of their webpages[2],
that some of their goals could be met nicely with what scrollkeeper
provides.  I got an email about the gwm earlier, and I've asked them if
they have contact with the folks running the project, but I thought
people here might be interested as well.
	Greg

[Scrollkeeper-devel] (ad) >> HARVEST Your Own TARGETED Email LEADS <<

[san113 <sa...@am...>]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!-- saved from
url=(0125)file://C:\Documents%20and%20Settings\Administrator\Local%20Settings\Temporary%20Internet%20Files\Content.IE5\LOGQL34N\ad2.htm
-->
<!-- saved from url=(0022)http://internet.e-mail --><HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=ks_c_5601-1987">
<META content="MSHTML 5.50.4922.900" name=GENERATOR></HEAD>
<BODY>
<DIV style="BACKGROUND-COLOR: #ffffff">
<DIV>
<DIV>
<DIV><FONT face=Arial size=2><FONT face=Arial size=2><FONT face=Arial 
size=2><FONT face=Arial size=2>Dear Fellow Networker,</FONT> 
</FONT></FONT></FONT>
<P>
<P><FONT face=Arial size=2><FONT face=Arial size=2><FONT face=Arial size=2><FONT 
face=Arial size=2>Let's get this straight, <FONT color=#ff0000><EM>the only 
way</EM></FONT> <EM><FONT color=#ff0000>you can make money</FONT></EM> 
on</FONT></FONT></FONT></FONT> <BR><FONT face=Arial size=2><FONT face=Arial 
size=2><FONT face=Arial size=2><FONT face=Arial size=2>the Web...<FONT 
color=#ff0000>Bulk E-mail</FONT>. Legal, ethical, and responsible Bulk 
<BR>E-mail (<EM>not spamming</EM>) can make you rich! It applies whether 
<BR>you're an Australian, Asian, European or 
American.</FONT></FONT></FONT></FONT> </P></DIV></DIV></DIV></DIV>
<P><FONT face=Arial size=2><FONT face=Arial size=2><FONT face=Arial size=2><FONT 
face=Arial size=2><FONT face=Arial size=2><STRONG><FONT color=#ff0000>Bulk Email 
Is Not Spam</FONT>.....</STRONG>The Law says so. Only fear keeps <BR>you from 
getting FREE, TARGETED LEADS at will.</FONT></FONT></FONT></FONT></FONT></P>
<DIV style="BACKGROUND-COLOR: #ffffff">
<DIV>
<DIV>
<DIV>
<P><FONT face=Arial size=2><FONT face=Arial size=2><FONT face=Arial size=2><FONT 
color=#000080><STRONG>I will show you :</STRONG></FONT></FONT></FONT></FONT> 
</P></DIV></DIV></DIV></DIV>
<P><FONT face=Arial size=2><FONT face=Arial size=2><FONT face=Arial size=2>* The 
<FONT color=#000080><STRONG>Secrets Used By MasterCard, Polaroid, 
AOL</STRONG></FONT></FONT></FONT></FONT> <BR><FONT face=Arial size=2><FONT 
face=Arial size=2><FONT face=Arial size=2>* How to <FONT 
color=#000080><STRONG>Send Bulk Email 
Safely</STRONG></FONT></FONT></FONT></FONT> <BR><FONT face=Arial size=2><FONT 
face=Arial size=2><FONT face=Arial size=2>* Free Software to <FONT 
color=#000080><STRONG>Harvest Targeted E-mails</STRONG></FONT><BR>* Free 
Software to <FONT color=#000080><STRONG>Bulk Mail that will bypass your 
ISP</STRONG></FONT></FONT></FONT></FONT> <BR><FONT face=Arial size=2><FONT 
face=Arial size=2><FONT face=Arial size=2>and much much 
more</FONT></FONT></FONT> <FONT face=Arial size=2><FONT face=Arial size=2><FONT 
face=Arial size=2>&nbsp;</FONT></FONT></FONT> </P>
<P><FONT face=Arial size=2><FONT face=Arial size=2><FONT face=Arial 
size=2>+++++++++++++++++++++++++++++++++++++++++++++++</FONT></FONT></FONT> 
<BR><FONT face=Arial size=2><FONT face=Arial size=2><FONT face=Arial 
size=2><STRONG>I seek your permission</STRONG> to send you&nbsp;the<FONT 
face=Arial size=2> **FREE** new booklet, <BR><STRONG><FONT color=#ff0000>"The 
Untold Secrets to Wealth on the Web"</FONT></STRONG> 
today.</FONT></FONT></FONT></FONT> <BR><FONT face=Arial size=2><FONT face=Arial 
size=2><FONT face=Arial 
size=2>+++++++++++++++++++++++++++++++++++++++++++++++</FONT></FONT></FONT> 
<BR><FONT face=Arial size=2><FONT face=Arial size=2><FONT face=Arial 
size=2><FONT face=Arial size=2><FONT size=1>If you're not </FONT></FONT><FONT 
face=Arial size=1>interested, please go to the end of this email &amp; click 
remove.</FONT></FONT></FONT></FONT> </P>
<P><FONT face=Arial size=2><FONT face=Arial size=2><FONT face=Arial size=2><FONT 
face=Arial size=2>Get your message to the millions of people on the Web who 
<BR>need or want your service &amp; product. </FONT></FONT></FONT></FONT></P>
<P><FONT face=Arial size=2><FONT face=Arial size=2><FONT face=Arial size=2><FONT 
face=Arial><FONT size=2><FONT face=Arial><FONT 
size=2>************************************************************************<BR><STRONG><FONT 
color=#000080><EM>I like you <U>could never get enough traffic/hits to my 
site</U>. <BR>I tried everything from <FONT color=#ff0000>FFAs </FONT>to <FONT 
color=#ff0000>search engines </FONT>&amp; even <FONT 
color=#ff0000>Leads</FONT><BR>which didn't work at all !</EM> 
<BR></FONT></STRONG>***********************************************************************</FONT></FONT></FONT></FONT></FONT></FONT></FONT> 
</P>
<DIV style="BACKGROUND-COLOR: #ffffff">
<DIV>
<DIV>
<DIV>
<P><FONT face=Arial size=2><FONT face=Arial size=2><FONT face=Arial size=2><FONT 
size=3><STRONG><FONT color=#ff0000>Act Now 
!</FONT></STRONG></FONT></FONT></FONT></FONT></P>
<P><FONT face=Arial size=2><B>Just click </B></FONT><FONT face=Arial 
size=2><FONT face=Arial size=2><FONT face=Arial size=2><FONT size=2>: <A 
href="http://amtartha.codns.com">http://amtartha.</A><A 
href="http://amtartha.codns.com">codns.com</A> 
&nbsp;&nbsp;</FONT></FONT></FONT></FONT> </P></DIV></DIV></DIV></DIV>
<DIV style="BACKGROUND-COLOR: #ffffff">
<DIV>
<DIV>
<DIV>
<P>
<P><FONT face=Arial size=2><FONT size=2><B>I am well on my way to having not 
only increased hits but<BR>successful sales as well. Let </B><STRONG><B>2003 
</B></STRONG><B>be </B><STRONG><B>your year <BR>of Success 
!</B></STRONG></FONT></FONT><B> </B>
<P>
<P><FONT face=Arial size=2><FONT face=Arial size=2><FONT face=Arial size=2><FONT 
size=3><STRONG><FONT color=#ff0000>So don't miss this !</FONT></STRONG> 
</FONT></FONT></FONT></FONT></P>
<P><FONT face=Arial size=2><FONT face=Arial size=2><FONT face=Arial size=2><FONT 
size=2><STRONG>Just click</STRONG> : <A 
href="http://amtartha.codns.com">http://amtartha.</A><A 
href="http://amtartha.codns.com">codns.com</A> 
</FONT></FONT></FONT></FONT><BR></P>
<P>
<P><FONT face=Arial size=2><FONT face=Arial size=2><FONT face=Arial>To Your 
Success,<BR>Yeoung,s.H</FONT></FONT></FONT> </P></DIV></DIV></DIV></DIV>
<P><FONT face=Arial size=2><FONT face=Arial size=2><FONT 
face=Arial><BR></FONT></FONT></FONT></P>
<P>&nbsp;<SPAN style="FONT-SIZE: 9pt"><FONT size=2>&nbsp;<FONT face=&#177;&#188;&#184;&#178;&#195;&#188;>*We 
comply with proposed federal legislation regarding unsolicited commercial e-mail 
by providing you with a method for your e-mail address to be permanently removed 
from our database and any future mailings from our company. 
</FONT></FONT></SPAN></P><PRE>---------------------------------------------------------
To unsubscribe from future mailings please click the link below
<A href="mailto:rem...@am...?subject=remove">REMOVE_ME_NOW</A><A href="mailto:rem...@am...?subject=remove">
</A></PRE><FONT color=#000000></A></FONT></BODY></HTML>

[Scrollkeeper-devel] IT`S A VERY GOOD PROPOSAL,PLEASE READ

[<bel...@re...>]

My name is Diouf Belgore=2C working with a Benin=2C based International
consultancy and public relation firm=2C last year I attended a business
seminar held between 7th and 12th October 2002 in Nairobi=2C in the
course of this I had the privilege of meeting Chief Dagba Victor
Aboduurin=2C the president of Dantata Group of companies=2E Chief Dagba
is an accomplished businessman and millionaire farmer in Africa=2C
specializing in cattle farms and various other agricultural produce
for export=2E He has farms in different countries of Africa=2E On getting
to know my profession=2C He took me into confidence by informing me
about the huge amount of money he spends on the purchase of a certain
serum=3B according to him he buys this product in excess of 200 jugs
=281000 liter=29 per month=2C for distription and a good portion for his
cattle=2E We got this far in our discussion
because he was hoping that my company could source for the product
cheaper for him considering the recent trends of falls in the general
price of beef in the world market=2C which is affecting his business=2E
Back to my office=2C I discussed this business proposal with my
director=2C and he decided we should scout for the producer of this
product=2E Lucky enough we found some in America and in Europe=2C we then
decided to deal with the company in Europe considering the ease of
importation and price of 2000=2E00US$ per liter=2E We then made proposal
to Chief Dagba to supply at $4=2C500 USD per litre=2C this he accepted
after ascertaining the component of the products=2C besides he has been
paying more than $5=2C500=2E00 for the product=2E For my role in securing
the contract my boss promised me a commission of 10% of whatever
profit made on each supply=2E But to my amazement after the first
supply of 20 jugs =2880 liter=29 was made Dantata Farms in November 2002
my director re
fuse giving me anything close to the agreed percentage=2C but gave me
only what he termed a bonus since am still his employee=2C upon my
protestation he threatened me with a dismissal from his company=2E I
decided to overlook his betrayal=2C but since then our relationship has
seized to be cordial=2E He never said anything to me again about the
supply=2E Just last week=2C I intercepted some mails from Dantata Farms
to my boss=2C I was shocked to learn that he has made two more supply
300 jugs of Genevoboost 2000mg and 320 Evoboost2100mg following a
suspected out break of diseases among his genetically engineered
cattle in Mali=2E He has
requested that these supplies be made before the 17th of june
2003=2EThis letter have not gotten to my boss and never will=2C I called
Chief Dagba telling him that my director is on sick leave to America
not returning until the end of June=2C I also informed him of a new
producer ready to supply at $4=2C200USD per liter=2C this he believed
because of my track record=2E In the light of the above=2C am therefore
seeking your cooperation in meeting up with the contract=2C as you know
this is highly lucrative business that promises 100% gain within
30days=2C all I am asking for is 20% commission=2E The main reason why am
contacting you is because I know you can be trusted and I cannot
handle this from my office with my boss not knowing about it=2E Should
you be interested please contact me=2C so that we can discuss the
modalities=2C I will be glad to give you the contact of the manufacture
in Europe=2E This you will keep to yourself=2C because if Chief Dagba
knows our source of th
e product=2C nothing stops him from buying directly there by putting
us out of business=2E
I hope to hearing from you soon=2E
Sincerely Yours=2C
Diouf Belgore=2E
Email =3Abeldiouf=40excite=2Ecom



 


 

Re: [Scrollkeeper-devel] about sending new/updated translations

[Malcolm T. <ma...@co...>]

On Fri, May 16, 2003 at 10:48:13AM +0200, Miloslav Trmac wrote:
> On Fri, May 16, 2003 at 09:21:42AM +0200, Luca Ferretti wrote:
> > Results? How can I send my translation now?
> I'm also missing this.
> 
> I can set ScrollKeeper up at the translation project and take care
> of commiting the incoming translations if nobody else has time.

The resolution of the most recent thread was to set up a Translation
Project account (or whatever they call it) for Scrollkeeper. The po
files in extra-po in the GNOME CVS were to be removed. Dan wanted to
wait a couple of days on this so that he could get things synchronised
and then was going to make the change.

So I guess we need to find out where Mr Muet is up to, but my guess
would be that if Miroslav has the time to coordinate this, he's going to
be elected unopposed as soon as Dan reads his mail. :-)

Cheers,
Malcolm

-- 
Quantum mechanics: the dreams stuff is made of.

Re: [Scrollkeeper-devel] about sending new/updated translations

[Miloslav T. <mi...@vo...>]

On Fri, May 16, 2003 at 09:21:42AM +0200, Luca Ferretti wrote:
> Results? How can I send my translation now?
I'm also missing this.

I can set ScrollKeeper up at the translation project and take care
of commiting the incoming translations if nobody else has time.
	Mirek

[Scrollkeeper-devel] about sending new/updated translations

[Luca F. <ell...@li...>]

Hi,
I remember a thread about using FSF tp or gnome cvs.

Results? How can I send my translation now?

Cheers, 
Luca

-- 
Think bigger

			My uncle

Re: [Scrollkeeper-devel] problem with configure script on scrollkeeper 0.3.12 *SOLVED!*

[Joel S. <js...@co...>]

That is good news.  I was wondering why your configure script was being
absolutist about versions, but then there are many reasons sometimes.  I
will pass this on to the sourcemage team since we are currently
considering how to fix the bug on our side ;).

 On Tue, 06 May 2003 11:53:45 +1000
Malcolm Tredinnick <ma...@co...> wrote:

> On Mon, May 05, 2003 at 04:03:06PM -0500, Joel Sinor wrote:
> > I have since got further information from the Sourcemage team:
> > > This was done because in the devel grimoire docbook-dtd is at
> > > version 4.2.0 and since scrollkeeper isn't updating to use it we
> > > had to do that script to stop the build process from failing.  If
> > > the test and stable grimoires are not updated to the docbook-dtd
> > > 4.2.0 then that needs to be removed for them.
> > > 
> > 
> > I of course replied the following:
> > Aha! To be fair, Eric was nice enough to send me a list of all the
> > bugs, and I just haven't gotten round to reading up on them and
> > submitting my own.  Actually my plan was once I figured out why it
> > was done to figure out a better fix.  Requiring that the docbook
> > *NOT* be installed is IMHO a bad way to fix this problem.  
> > As for test and stable, well, they will of course catch up with
> > where devel is now eventually, but this begs the question of what
> > happens if I install the new version of the dtd?  (Before I got this
> > error I knew pretty much zero about docbook, and even aftre I pretty
> > much only know what happens when you use the commands in
> > scrollkeeper's configure script ;) )  I mean will tests for the old
> > version still say it is there(will it be there?) or when it is
> > upgraded is it replaced completely with no trace it was ever there?
> > 
> > ---
> > Anyhow, I am wondering if you guys can answer my docbook questions. 
> > I am working on a better way to fix the sourcemage problem.  I am
> > leaning currently toward making the "sedit" on the version number of
> > the docbook dtd rather than doing what they were doing before, which
> > is making it so that the dtd cannot be installed if you want to
> > install scrollkeeper.
> 
> I have lost track a bit of what is quoting from other sources and
> what is directed to this list in the above, but it doesn't really
> matter.
> 
> To try and clear this matter up: the problem is because scrollkeeper
> does not currently detect the absolutely latest verison of Docbook.
> That is a bug in Scrollkeeper. There is even now a bug at sourceforge
> for it(filed a few days ago). It will be fixed by making configuration
> scripts for scrollkeeper try to detect a few different Docbook
> versions, falling back from most recent to oldest. Once that change is
> made, it will be easy to handle future Docbook upgrades.
> 
> Hopefully this should make everybody happy and prevent a reoccurence
> of this debacle in the future.
> 
> Malcolm
> 
> -- 
> Experience is something you don't get until just after you need it.
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Scrollkeeper-devel mailing list
> Scr...@li...
> https://lists.sourceforge.net/lists/listinfo/scrollkeeper-devel

[Scrollkeeper-devel] Solaris and Scrollkeeper

[Chip C. <wil...@mc...>]

QWxsLA0KDQpIYXMgYW55b25lIGJlZW4gYWJsZSB0byBvciBoZWFyZCBvZiBhbnlvbmUgYmVpbmcg
YWJsZSB0byBzdWNjZXNzZnVsbHkgY29tcGlsZSBTY3JvbGxrZWVwZXIgYW5kIGl0cyByZXF1aXJl
ZCBsaWJyYXJpZXMgb24gU29sYXJpcyA4Pw0KDQpDaGlw

Re: [Scrollkeeper-devel] problem with configure script on scrollkeeper 0.3.12 *SOLVED!*

[Malcolm T. <ma...@co...>]

On Mon, May 05, 2003 at 04:03:06PM -0500, Joel Sinor wrote:
> I have since got further information from the Sourcemage team:
> > This was done because in the devel grimoire docbook-dtd is at version
> > 4.2.0 and since scrollkeeper isn't updating to use it we had to do
> > that script to stop the build process from failing.  If the test and
> > stable grimoires are not updated to the docbook-dtd 4.2.0 then that
> > needs to be removed for them.
> > 
> 
> I of course replied the following:
> Aha! To be fair, Eric was nice enough to send me a list of all the bugs,
> and I just haven't gotten round to reading up on them and submitting my
> own.  Actually my plan was once I figured out why it was done to figure
> out a better fix.  Requiring that the docbook *NOT* be installed is IMHO
> a bad way to fix this problem.  
> As for test and stable, well, they will of course catch up with where
> devel is now eventually, but this begs the question of what happens if I
> install the new version of the dtd?  (Before I got this error I knew
> pretty much zero about docbook, and even aftre I pretty much only know
> what happens when you use the commands in scrollkeeper's configure
> script ;) )  I mean will tests for the old version still say it is there
> (will it be there?) or when it is upgraded is it replaced completely
> with no trace it was ever there?
> 
> ---
> Anyhow, I am wondering if you guys can answer my docbook questions.  I
> am working on a better way to fix the sourcemage problem.  I am leaning
> currently toward making the "sedit" on the version number of the docbook
> dtd rather than doing what they were doing before, which is making it so
> that the dtd cannot be installed if you want to install scrollkeeper.

I have lost track a bit of what is quoting from other sources and
what is directed to this list in the above, but it doesn't really
matter.

To try and clear this matter up: the problem is because scrollkeeper
does not currently detect the absolutely latest verison of Docbook. That
is a bug in Scrollkeeper. There is even now a bug at sourceforge for it
(filed a few days ago). It will be fixed by making configuration
scripts for scrollkeeper try to detect a few different Docbook versions,
falling back from most recent to oldest. Once that change is made, it
will be easy to handle future Docbook upgrades.

Hopefully this should make everybody happy and prevent a reoccurence of
this debacle in the future.

Malcolm

-- 
Experience is something you don't get until just after you need it.

Re: [Scrollkeeper-devel] problem with configure script on scrollkeeper 0.3.12 *SOLVED!*

[Joel S. <js...@co...>]

I have since got further information from the Sourcemage team:
> This was done because in the devel grimoire docbook-dtd is at version
> 4.2.0 and since scrollkeeper isn't updating to use it we had to do
> that script to stop the build process from failing.  If the test and
> stable grimoires are not updated to the docbook-dtd 4.2.0 then that
> needs to be removed for them.
> 

I of course replied the following:
Aha! To be fair, Eric was nice enough to send me a list of all the bugs,
and I just haven't gotten round to reading up on them and submitting my
own.  Actually my plan was once I figured out why it was done to figure
out a better fix.  Requiring that the docbook *NOT* be installed is IMHO
a bad way to fix this problem.  
As for test and stable, well, they will of course catch up with where
devel is now eventually, but this begs the question of what happens if I
install the new version of the dtd?  (Before I got this error I knew
pretty much zero about docbook, and even aftre I pretty much only know
what happens when you use the commands in scrollkeeper's configure
script ;) )  I mean will tests for the old version still say it is there
(will it be there?) or when it is upgraded is it replaced completely
with no trace it was ever there?

---
Anyhow, I am wondering if you guys can answer my docbook questions.  I
am working on a better way to fix the sourcemage problem.  I am leaning
currently toward making the "sedit" on the version number of the docbook
dtd rather than doing what they were doing before, which is making it so
that the dtd cannot be installed if you want to install scrollkeeper.


 On Thu, 01 May 2003 20:49:43 +1000
Malcolm Tredinnick <ma...@co...> wrote:

> On Thu, May 01, 2003 at 02:35:20AM -0500, Joel Sinor wrote:
> > I forgot to mention that I did eventually find out what was
> > happening with Sourcemage.  Now, compiling by hand would have worked
> > in any case. At issue was a change they made for a bug.  I have not
> > tracked the bug # down and corrected it, but essentially they were
> > doing$ more /var/lib/sorcery/codex/stable/gnome/scrollkeeper/BUILD
> > (
> >   sedit "s/if xmlcatalog/if ! xmlcatalog/" configure
> >   default_build
> > ) > $C_FIFO 2>&1
> > $ 
> 
> Because they don't believe in "patch"?
> 
> > So essentially my theory is someone got the error for the DTD not
> > being there and changed this so they would not get the error.  I
> > will find out why eventually, but this of course has the result that
> > if you have the dependency installed you will fail.  Sourcemage
> > usually has things like this in their spell script config files to
> > fix broken ./configure and make files (or at least things that are
> > broken for their distro). This will not affect any normal
> > compilations, just compiles using their scripts.  I will let you
> > guys know when I find out more (have been fighting other battles).
> 
> Thanks for letting us know. That unfortunately reaffirms my earlier
> point though that, at least in my mind, Sourcemage are well on truly
> on the "distributions not be trusted in bug reports" list, which is
> going to really suck for their users. Completely breaking a package
> rather than fixing the core problem is disgraceful -- and you seem to
> indicate they do it often. There just are not that many 'broken' build
> processes out there that it's worth adopting a lax attitude to change.
> Those that are broken should be patched and bugs reported upstream to
> confirm that it really is a bug (this example was "fixed" by somebody
> who doesn't understand document build processes, for example).
> 
> Sorry, I'll stop ranting now. But really!
> 
> Not your fault though and thanks for the update. I'm going to go and
> have a lie down now.
> 
> Malcolm
> 
> -- 
> Tolkien is hobbit-forming.
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Scrollkeeper-devel mailing list
> Scr...@li...
> https://lists.sourceforge.net/lists/listinfo/scrollkeeper-devel

Re: [Scrollkeeper-devel] API to get the count of newly added omffiles

[Rajkumar S. <raj...@wi...>]

Hi Dan,

Thanks for your comments and motivation.


> These sound like good additions.  I would hope that not many packages
> forget to run updatedb.  Especially since many users don't have root
> access on their machines.  (It might make sense to have a crontab entry
> installed to run updatedb daily, although I'm not sure how uniform cron is
> handled across distributions and different flavors of Unix.)  However, I
> think this utility is a good thing to have.

- Yes, I do agree that packages should run updatedb by default, but
there are some odd cases where it fails to run it, in those cases the
help browser can make use of this API to know if there are any
unregistered omf files, if there are any it could popup a message
saying:

"Newly installed app. detected, pls. ask your admin to run
scrollkeeper_update to view the help doc's for the app".

 
> Further, we have had intentions to export an API for some time.  In fact,
> many of the things which are now scripts should be put into a library.
> Your present work could be the start of the exported API and then we can
> expand it from there.
> 
> Thanks for the contributions :)

- Sure :) Once I finish with the API I'll post in the list for
review/approval.


Thanks & Regards,
Raj.

Re: [Scrollkeeper-devel] Small bug tracker cleanup

[Dan M. <mu...@al...>]

On Fri, 25 Apr 2003, Miloslav Trmac wrote:

> Can I commit the patches?

Mirek,

Thanks for going through the bug list.  Go ahead and commit the fixes.

> Also, the bugs should be closed/modified, I can't do that.

I just changed your permissions so you should be able to close/modify 
bugs.  If you still have any problems, email me.

-Dan

Re: [Scrollkeeper-devel] API to get the count of newly added omf files

[Dan M. <mu...@al...>]

Hi Raj,

These sound like good additions.  I would hope that not many packages
forget to run updatedb.  Especially since many users don't have root
access on their machines.  (It might make sense to have a crontab entry
installed to run updatedb daily, although I'm not sure how uniform cron is
handled across distributions and different flavors of Unix.)  However, I
think this utility is a good thing to have.

Further, we have had intentions to export an API for some time.  In fact,
many of the things which are now scripts should be put into a library.  
Your present work could be the start of the exported API and then we can
expand it from there.

Thanks for the contributions :)

Cheers,

Dan

On Wed, 30 Apr 2003, Rajkumar Sivasamy wrote:

> Hi,
> 
> This is further in continuation of my earlier mail about "Indication of
> newly added omf file". On further analysis I wrote a small API say
> scrollkeeper_get_omffile_count() in update.c which will return the count
> of omf files that needs to be registered/unregistered with
> scrollkeeper_docs.
> 
> With the help of this API any help browser would know if there are any
> newly installed omf files that needs to be registered and if so it can
> prompt a message to the user asking him to run 'scrollkeeper_update' to
> register them.
> 
> 
> Issue in implementing the API:
> -----------------------------
> 
> I find that scrollkeeper doesn't have any API yet and hence there are no
> scrollkeeper .h files to export the API's, so for implementing this
> scrollkeeper_get_omffile_count() we would need to have a scrollkeeper .h
> file installed in standard path (like /usr/include/scrollkeeper/*).
> 
> Pls. let me know if we could move forward in implementing this API.
> 
> 
> Note: Am not sure if my previous mail sent on '25th Apr 2003' was
> delivered to this list as I couldn't see it in the archives list
> "http://sourceforge.net/mailarchive/forum.php?thread_id=2014500&forum_id=4112",
> hence am attaching my previous mail with it.
> 
> 
> Thanks & Regards,
> Raj.

Re: [Scrollkeeper-devel] problem with configure script on scrollkeeper 0.3.12 *SOLVED!*

[Malcolm T. <ma...@co...>]

On Thu, May 01, 2003 at 02:35:20AM -0500, Joel Sinor wrote:
> I forgot to mention that I did eventually find out what was happening
> with Sourcemage.  Now, compiling by hand would have worked in any case.
> At issue was a change they made for a bug.  I have not tracked the bug #
> down and corrected it, but essentially they were doing
> $ more /var/lib/sorcery/codex/stable/gnome/scrollkeeper/BUILD
> (
>   sedit "s/if xmlcatalog/if ! xmlcatalog/" configure
>   default_build
> ) > $C_FIFO 2>&1
> $ 

Because they don't believe in "patch"?

> So essentially my theory is someone got the error for the DTD not being
> there and changed this so they would not get the error.  I will find out
> why eventually, but this of course has the result that if you have the
> dependency installed you will fail.  Sourcemage usually has things like
> this in their spell script config files to fix broken ./configure and
> make files (or at least things that are broken for their distro).
> This will not affect any normal compilations, just compiles using their
> scripts.  I will let you guys know when I find out more (have been
> fighting other battles).

Thanks for letting us know. That unfortunately reaffirms my earlier
point though that, at least in my mind, Sourcemage are well on truly on
the "distributions not be trusted in bug reports" list, which is going
to really suck for their users. Completely breaking a package rather
than fixing the core problem is disgraceful -- and you seem to indicate
they do it often. There just are not that many 'broken' build processes
out there that it's worth adopting a lax attitude to change. Those that
are broken should be patched and bugs reported upstream to confirm that
it really is a bug (this example was "fixed" by somebody who doesn't
understand document build processes, for example).

Sorry, I'll stop ranting now. But really!

Not your fault though and thanks for the update. I'm going to go and
have a lie down now.

Malcolm

-- 
Tolkien is hobbit-forming.