firebird-docs — chat stuff about documentation

[Firebird-docs] Postgres docs

[Robert (J. M. <rj...@ar...>]

I've been meaning to suggest this for ages, but has anyone considerd
adapting the postgres docs for firebird? The copyright would allow
it:
http://www.postgresql.org/docs/7.4/static/LEGALNOTICE.html

It's already docbook. We could just work through it, changing
everything to be how firebird does it. Some parts would need almost
no modification at all (like most of the SQL), some parts would end
up total rewrites, but having the postgres as examples would still
help ensure that coverage was good (ie. if we answer every question
that they answer then we have answered most of the common
questions).

Robert Munro

[Firebird-docs] Firebird :: PHP :: Dreamweaver :: Phakt

[dso <ds...@sk...>]

I've created a document for using Firebird with Dreamweaver, PHP, 
Apache& Phakt. This topic is generally dominated by the MySQL camp so I 
though it might help the growth of Firebird if there was a good 
outlining how to use these programs together.

Please feel free to read over it and see if you can pickup any mistakes. 
It is licensed with the GNU Free Documentation License, so pass it around.

The document is in PDF format and can be found at the following address:

http://www.methyl.ca/pdf/DMX-PHP-FB.pdf

Darcy

Re: [Firebird-docs] Using IB docs as inspiration

[Paul V. <pa...@vi...>]

Hi Nigel,

> When Firebird split away from Borland, were there any agreements on
> how much info from the IB6 docs could be used in documentation for
> Firebird?

No. They didn't include the docs in the IPL package. We asked them
several times if we could use those docs "as if the fell under the
IPL". They never answered.

> Percentages? No cut and paste (But manual typing allowed)?

For copyrights it doesn't matter *how* you copy text. Whether you
copy-and-paste or retype, as soon as it's more than a loose sentence
here and there it's a possible copyright violation.

All this goes for the text. The information as such is public, and we
can use it.

> Can we use the framework, but not the content(and come up with the
> content ourselves?)

The framework is a grey area, I think. Copyright laws protect
everything that's unique in a work. Borland could argue that the
document structure is a specific one that *they* came up with, and
that the chance that someone else would *independently* come up with
the same structure is close to zero.

The more general the structure is (think of a reference guide with the
functions ordered alphabetically) the less chance the author can win a
copyright lawsuit if someone else uses it too. (Same goes for text by
the way: try copyrighting "It's raining today".)

Anyway, to be safe I would build my docs from the ground up. But of
course you can learn from existing docs. See what their strong points
are, and what can be done better.

> It'd be just sooo easy to drag and drop...but it's very naughty!

Actually Tilo and I have been doing that for months last year. But it
was a DRAG and we decided to DROP it when it became clear that Borland
just wouldn't give permission to publish our homework ;-)

With hindsight, it has only cost us time. It just was the wrong track.

> (PocketBooks are now continuing)
> http://oc.aims.net.au/pb/fb/

I'll have a look.


Greetings,
Paul Vinkenoog

[Firebird-docs] Using IB docs as inspiration

[Nigel W. <ni...@e-...>]

When Firebird split away from Borland, were there any agreements on how much
info from the IB6 docs could be used in documentation for Firebird?

Percentages? No cut and paste (But manual typing allowed)?

Can we use the framework, but not the content(and come up with the content
ourselves?)

It'd be just sooo easy to drag and drop...but it's very naughty!

(PocketBooks are now continuing)
http://oc.aims.net.au/pb/fb/

Nigel

Re: [Firebird-docs] Looking for interbase/firebird c client api docs

[Paul V. <pa...@vi...>]

Hi Kevin,

[ Firebird API docs ]

> Subject says it all
> ie the ibase.h interface

For now you'll have to use the InterBase API Guide plus the Release
Notes that came with your Firebird version.

The InterBase API Guide is here:

  http://www.ibphoenix.com/downloads/60ApiGuide.zip

Or get the entire, cross-indexed, InterBase doc set:

  http://www.ibphoenix.com/downloads/60All.zip


Greetings,
Paul Vinkenoog

[Firebird-docs] Looking for interbase/firebird c client api docs

[Kevin T. <te...@ya...>]

Subject says it all
ie the ibase.h interface

Re: [Firebird-docs] How to contribute

[Paul V. <pa...@vi...>]

Hi Michael,

> I will work on a proposed structure for a SQL-Reference chapter a
> little in the next weeks (can't really start up before my exams in
> 2 weeks).

Great! Welcome aboard - and good luck with your exams of course :-)

(Uni Passau, gell?)

> Would you think it's sensible to include the packaged udf-library
> functions with the SQL reference? I was really bugged until I
> finally found them ...

I think it's a good idea - after all, we use those UDFs in SQL
statements, side by side with the internal SQL functions. But we have
to clearly mark each entry as either internal SQL or UDF. And if we do
this, I think we should also include each UDF's declaration for the
reader to copy-and-paste.


Greetings,
Paul Vinkenoog

Re: [Firebird-docs] How to contribute

[Michael G. <gl...@ok...>]

Hi,

>>I would like to contribute some to the Firebird documentation. As to
>>prevent overlapings, I would like to know what area to get working
>>in.
> 
> 
> There's a lot of ground yet to be covered. Within the Firebird manual
> module at SourceForge, we now only have an Introduction, an MS-SQL to
> Firebird Migration Guide, and a couple of Howtos for docwriters.
> Lester Caine is working on a table of reserved words + glossary; Nigel
> Weeks has set up a Firebird Pocketbook at http://oc.aims.net.au/pb/fb/
> (of which we will probably convert stuff to put in the module later);
> and myself I'll be attacking the Firebird API.
> 
> If you want to contribute work to the manual module, please read
> the Howtos at http://vinkenoog.nl//firebird/drafthowto/ (temporary
> location).

I allready checked out the module and read through the things which are 
there so far. I have some docbook experience allready and I quite like 
it, so I am happy to see it used for Firebird docs too. The docwriter 
howtos look quite sensible to me, too :)

>>I have considered adding some things allready available in the stuff
>>at ibphoenix (like the SQL command reference, etc.) to the docs. I
>>think this should be done so the docs can be edited and new
>>Firebird-Related stuff can be added (like firebird supporting
>>ANSI-style CASE).
> 
> An SQL reference would be a *great* contribution IMO. But beware! The
> InterBase SQL Reference is (c) Borland, even if they don't state that
> explicitly in the document. If you want to use it as a basis and then
> add or change things where needed, you must have Borland's permission
> - which they probably won't give you (we've been there too).
 >
> Without that permission, you *can* use the information found in that
> document, but you would have to reword every paragraph and probably
> also use a different structure in order to be legally safe. A lot of
> work, but if you want to make a start with it: great. Anything else is
> appreciated too of course. Please also stay on the firebird-docs list
> so we can exchange ideas, and know from each other what we are doing.

Ah yes, I allready suspected that. So I will be very careful about not 
copying anything out of the IB-Manuals. I will work on a proposed 
structure for a SQL-Reference chapter a little in the next weeks (can't 
really start up before my exams in 2 weeks).

Would you think it's sensible to include the packaged udf-library 
functions with the SQL reference? I was really bugged until I finally 
found them ...

Michael

Re: [Firebird-docs] How to contribute

[Paul V. <pa...@vi...>]

Hello Michael,

> I would like to contribute some to the Firebird documentation. As to
> prevent overlapings, I would like to know what area to get working
> in.

There's a lot of ground yet to be covered. Within the Firebird manual
module at SourceForge, we now only have an Introduction, an MS-SQL to
Firebird Migration Guide, and a couple of Howtos for docwriters.
Lester Caine is working on a table of reserved words + glossary; Nigel
Weeks has set up a Firebird Pocketbook at http://oc.aims.net.au/pb/fb/
(of which we will probably convert stuff to put in the module later);
and myself I'll be attacking the Firebird API.

If you want to contribute work to the manual module, please read
the Howtos at http://vinkenoog.nl//firebird/drafthowto/ (temporary
location).

> I have considered adding some things allready available in the stuff
> at ibphoenix (like the SQL command reference, etc.) to the docs. I
> think this should be done so the docs can be edited and new
> Firebird-Related stuff can be added (like firebird supporting
> ANSI-style CASE).

An SQL reference would be a *great* contribution IMO. But beware! The
InterBase SQL Reference is (c) Borland, even if they don't state that
explicitly in the document. If you want to use it as a basis and then
add or change things where needed, you must have Borland's permission
- which they probably won't give you (we've been there too).

Without that permission, you *can* use the information found in that
document, but you would have to reword every paragraph and probably
also use a different structure in order to be legally safe. A lot of
work, but if you want to make a start with it: great. Anything else is
appreciated too of course. Please also stay on the firebird-docs list
so we can exchange ideas, and know from each other what we are doing.


Greetings,
Paul Vinkenoog

[Firebird-docs] How to contribute

[Michael G. <gl...@ok...>]

Hi,

I would like to contribute some to the Firebird documentation. As to 
prevent overlapings, I would like to know what area to get working in.

I have considered adding some things allready available in the stuff at 
ibphoenix (like the SQL command reference, etc.) to the docs. I think 
this should be done so the docs can be edited and new Firebird-Related 
stuff can be added (like firebird supporting ANSI-style CASE).

If thats okay for you, I will start working on this.

Michael

Re: [Firebird-docs] Howtos committed

[Paul V. <pa...@vi...>]

Hi Lester,

[ Howtos committed ]

> OK I can see them from Eclipse, now the Sourceforge is back up
> again.
> It would be nice to have a 'compiled' copy in html perhaps in
> an 'html' directory?

We only put the sources in CVS, not the rendered docs. I'll send a
message to the website list about having an HTML version placed on the
documentation pages at firebird.sourceforge.net - I think Pavel Cisar
is in control of this.

For the time being you can read the howtos at this temporary location:

  http://vinkenoog.nl/firebird/drafthowto/

You can also build the HTML version yourself; see the Docbuilding
Howto and/or the Readme in the manual directory.

For now the PDF output is terrible (try "build pdf"); until we improve
that I think we shouldn't publish the PDF version.

> Are you going to throw the reserved word list there?

Yes, when it's ready. All the XML docs wind up in
/manual/src/docs/firebirddocs, except the main document
firebirddocs.xml, which is in /manual/src/docs


Greetings,
Paul Vinkenoog

Re: [Firebird-docs] Howtos committed

[Lester C. <le...@ls...>]

Paul Vinkenoog wrote:

> Yesterday afternoon I've added the Docbuilding Howto and the
> Docwriting Howto to the manual module. I've also committed the
> improved firebirddocs.css stylesheet and removed the obsolete
> images in src/docs/images/callouts

OK I can see them from Eclipse, now the Sourceforge is back 
up again.
It would be nice to have a 'compiled' copy in html perhaps 
in an 'html' directory?

Are you going to throw the reserved word list there?
I have a 'borrowed' glossary (thanks Helen), but until I've 
tUrned all the 'red' text to 'black' ( redefined from 
firebird sources ) I can't put that over ;)

-- 
Lester Caine
-----------------------------
L.S.Caine Electronic Services

[Firebird-docs] Howtos committed

[Paul V. <pa...@vi...>]

Hello all,

Yesterday afternoon I've added the Docbuilding Howto and the
Docwriting Howto to the manual module. I've also committed the
improved firebirddocs.css stylesheet and removed the obsolete
images in src/docs/images/callouts


Greetings,
Paul Vinkenoog

[Firebird-docs] Re: Reserved words

[Paul V. <pa...@vi...>]

Hi Lester,

> The list does seem a bit slow in responding? Paul's message came
> through lunchtime yesterday, by midnight the list copy still had
> not appeared.

Yes, but that's very very rare. I usually see my own messages back in
minutes. Maybe it had something to do with the current virus storm.

> The CVS server seems to be down at the moment so I can't look,
> should the Glossary be a separate file to the base list?

If it's a glossary of reserved words only, I think it should be in one
document with the table. A DocBook XML document can be spread over
several files if you want to, but this sometimes results in practical
inconveniences if you edit them with XMLMind. Better leave them in
one file; you can always collapse the first section if you want to
concentrate on the glossary, and vice versa.

BTW, after rendering the glossary is automatically placed in a
separate HTML document, just like major <section>s wind up in a
file of their own (at least in the defaulthtml build target).

> Is it worth my taking the PHP starter guide and converting it? I
> also have the basis for a Linux version which the guys(and galls)
> on the php list are helping to fill out.

Sounds like a good idea to me!


Greetings,
Paul Vinkenoog

Re: [Firebird-docs] docs of firebird

[Paul V. <pa...@vi...>]

Hello German,

> Please I see examples directory, but I don't see an sample with
> tcp/ip conection. I need information for it. For Firebird ( the best
> database c/s ) and c with gnu/gpl project. Please where can I get
> docs and samples for ibase.h api or/and gds.h header file ?

Look in the InterBase API Guide & Reference, at
  http://www.ibphoenix.com/downloads/60ApiGuide.zip

Also check the Firebird Release Notes for changes.

> and gpre ?

In the InterBase Embedded SQL Guide:
  http://www.ibphoenix.com/downloads/60EmbedSQL.zip

You can also get all the InterBase docs in one big zip:
  http://www.ibphoenix.com/downloads/60All.zip


Greetings,
Paul Vinkenoog

Re: [Firebird-docs] Re: Reserved words

[Helen B. <he...@tp...>]

At 07:34 AM 31/01/2004 +0000, Lester Caine wrote:
>Helen Borrie wrote:
>
>>>[ reserved words glossary ]
>>>
>>> > Is there an existing one ? I have not looked properly yet ;)
>>>
>>>None that I know of, but then: I haven't looked *at all* ;-)
>>Get the list this way:
>>List from the LangRef of the IB6 Beta docs (look up "Keywords")
>>+
>>List from the release notes of the IB6 Beta docs
>>+
>>List from the Firebird 1.5 release notes.
>>Then you will have them all.
>
>We have the LIST now, the next step is a GLOSSARY to go with it. If there 
>is nothing already existing, then I will start filling one. Paul has 
>converted the list to XML and created a sample for the glossary elements.

Sorry, I missed that you were building a glossary of reserved words.  And 
you're right, in the IB docs they are not indexed reliably.

Have you looked at this:

http://www.ocelot.ca/glossary.htm

Helen

Re: [Firebird-docs] Re: Reserved words

[Lester C. <le...@ls...>]

Helen Borrie wrote:

>> [ reserved words glossary ]
>>
>> > Is there an existing one ? I have not looked properly yet ;)
>>
>> None that I know of, but then: I haven't looked *at all* ;-)
> 
> Get the list this way:
> 
> List from the LangRef of the IB6 Beta docs (look up "Keywords")
> +
> List from the release notes of the IB6 Beta docs
> +
> List from the Firebird 1.5 release notes.
> 
> Then you will have them all.

We have the LIST now, the next step is a GLOSSARY to go with 
it. If there is nothing already existing, then I will start 
filling one. Paul has converted the list to XML and created 
a sample for the glossary elements.

>> > If there isn't perhaps that is something I can start pulling
>> > together?
>>
>> That would be great (unless we find an existing one we can use).

Given the original language reference you gave doesn't have 
much detail, I presume I will have to do some digging :)

>> > As I think I said before, I an using Eclipse to manage the PHP,JS
>> > and CSS stuff and it handles XML as well, but needs some help there
>> > still - such as a decent viewer :)
>>
>> I didn't know anything about Eclipse. I've looked up their website
>> just now, did some reading, and downloaded it. Looks very promising!

The more I start to get into Eclipse, the more I like it. 
Sun are suggesting that it's only the same as NetBeans, BUT 
NetBeans can't handle ( as far as I can find out ) PHP 
development and debugging, javascript, and I'm now looking 
at C++ Since BuilderX is going to be another expensive bug 
fix ( when them finish it ;) ). I haven't thought about 
using  Eclipse for Java at all.
The CVS client is great, a lot more user friendly than the 
options I had played with so far. It might even convince me 
to drop FreeVCS (using Firebird) and switch to CVS my self!

>> > column (GROUP_COMMIT_WAIT_TIME) but I can have a look at how that is
>> > managed.
>>
>> I was going to ask you about that, but forgot. I thought either you or
>> the original author had done that on purpose to keep the column width
>> within limits 

I think that is the answer - it was designed to print 
filling the page.

>> BTW: Let's take this conversation back to firebird-docs; maybe we can
>> get some useful input from others, but even if not, then at least they
>> can see what's going on.

The list does seem a bit slow in responding? Paul's message 
came through lunchtime yesterday, by midnight the list copy 
still had not appeared.

The CVS server seems to be down at the moment so I can't 
look, should the Glossary be a separate file to the base list?

Is it worth my taking the PHP starter guide and converting 
it? I also have the basis for a Linux version which the 
guys(and galls) on the php list are helping to fill out.

-- 
Lester Caine
-----------------------------
L.S.Caine Electronic Services

[Firebird-docs] docs of firebird

[german a. b. <ge...@te...>]

Hello to all

Please I see examples directory, but I don't see an sample with tcp/ip 
conection. I need information for it. For Firebird ( the best database 
c/s ) and c with gnu/gpl project. Please where can I get docs and 
samples for ibase.h api or/and gds.h header file ? and gpre ? Or other 
languaje/compiler free for create a binary files in gnu plataforms with 
more dococuments..

thanks to all

Re: [Firebird-docs] Re: Reserved words

[Helen B. <he...@tp...>]

At 01:23 PM 30/01/2004 +0100, Paul Vinkenoog wrote:
>Hello Lester,
>
>[ reserved words glossary ]
>
> > Is there an existing one ? I have not looked properly yet ;)
>
>None that I know of, but then: I haven't looked *at all* ;-)

Get the list this way:

List from the LangRef of the IB6 Beta docs (look up "Keywords")
+
List from the release notes of the IB6 Beta docs
+
List from the Firebird 1.5 release notes.

Then you will have them all.

Helen



> > If there isn't perhaps that is something I can start pulling
> > together?
>
>That would be great (unless we find an existing one we can use).
>
> > As I think I said before, I an using Eclipse to manage the PHP,JS
> > and CSS stuff and it handles XML as well, but needs some help there
> > still - such as a decent viewer :)
>
>I didn't know anything about Eclipse. I've looked up their website
>just now, did some reading, and downloaded it. Looks very promising!
>
> > Only problem I can see is that a couple of words wrap to the next
> > column (GROUP_COMMIT_WAIT_TIME) but I can have a look at how that is
> > managed.
>
>I was going to ask you about that, but forgot. I thought either you or
>the original author had done that on purpose to keep the column width
>within limits (it happens three times, each time when the word is
>really long), so I mimicked it in the XML. But I think it's ugly and
>confusing (people may think that these words belong to two columns) so
>we'd better change that.
>
>In the original HTML they've just created spans like this:
>
>       <td valign="top" colspan="2">
>         <p align="left"> GROUP_COMMIT_WAIT</p>
>       </td>
>
>In DocBook XML this is done like:
>
>       <entry namest="col-fb-only" nameend="col-sql92">
>         <para>GROUP_COMMIT_WAIT</para>
>       </entry>
>
>The values for namest (span's start col) and nameend (end col) must
>have been previously defined in the tgroup in order for this to work:
>
>       <tgroup cols="4">
>         <colspec colname="col-fb-and-sql99"/>
>         <colspec colname="col-fb-only"/>
>         <colspec colname="col-sql92"/>
>         <colspec colname="col-sql99-only"/>
>
>I've removed these spans from my XML version now; will attach it.
>
>BTW: Let's take this conversation back to firebird-docs; maybe we can
>get some useful input from others, but even if not, then at least they
>can see what's going on.
>
>
>Greetings,
>Paul Vinkenoog
>
>
>[ Cc: to firebird-docs ]
>
>
>
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by EclipseCon 2004
>Premiere Conference on Open Tools Development and Integration
>See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
>http://www.eclipsecon.org/osdn
>_______________________________________________
>Firebird-docs mailing list
>Fir...@li...
>https://lists.sourceforge.net/lists/listinfo/firebird-docs

[Firebird-docs] Re: Reserved words

[Paul V. <pa...@vi...>]

Hello Lester,

[ reserved words glossary ]

> Is there an existing one ? I have not looked properly yet ;)

None that I know of, but then: I haven't looked *at all* ;-)

> If there isn't perhaps that is something I can start pulling
> together?

That would be great (unless we find an existing one we can use).

> As I think I said before, I an using Eclipse to manage the PHP,JS
> and CSS stuff and it handles XML as well, but needs some help there
> still - such as a decent viewer :)

I didn't know anything about Eclipse. I've looked up their website
just now, did some reading, and downloaded it. Looks very promising!

> Only problem I can see is that a couple of words wrap to the next
> column (GROUP_COMMIT_WAIT_TIME) but I can have a look at how that is
> managed.

I was going to ask you about that, but forgot. I thought either you or
the original author had done that on purpose to keep the column width
within limits (it happens three times, each time when the word is
really long), so I mimicked it in the XML. But I think it's ugly and
confusing (people may think that these words belong to two columns) so
we'd better change that.

In the original HTML they've just created spans like this:

      <td valign="top" colspan="2">
        <p align="left"> GROUP_COMMIT_WAIT</p>
      </td>

In DocBook XML this is done like:

      <entry namest="col-fb-only" nameend="col-sql92">
        <para>GROUP_COMMIT_WAIT</para>
      </entry>

The values for namest (span's start col) and nameend (end col) must
have been previously defined in the tgroup in order for this to work:

      <tgroup cols="4">
        <colspec colname="col-fb-and-sql99"/>
        <colspec colname="col-fb-only"/>
        <colspec colname="col-sql92"/>
        <colspec colname="col-sql99-only"/>

I've removed these spans from my XML version now; will attach it.

BTW: Let's take this conversation back to firebird-docs; maybe we can
get some useful input from others, but even if not, then at least they
can see what's going on.


Greetings,
Paul Vinkenoog


[ Cc: to firebird-docs ]

Re: [Firebird-docs] Draft Docwriting Howto available

[Paul V. <pa...@vi...>]

Hi all,

> The Docwriting Howto is not yet completely finished, but everything
> you need to know about DocBook is in there now. I placed it at
>
>   http://vinkenoog.nl/firebird/drafthowto/

It's complete now.

One concern I have is that the DocBook stuff makes it very bulky. But
we need it, because without this knowledge people just can't write
docs. I've been thinking that maybe I should put all the DocBook
sections in a separate Howto. That would make the Docwriting Howto
simpler, but it would raise the number of Howtos to read to three...

Not sure which is the best choice here. Your opinions are welcome.


Greetings,
Paul Vinkenoog

Re: [Firebird-docs] Reserved Words

[Paul V. <pa...@vi...>]

Hi Lester,

[ reserved words ]

> Not being able to find a complete list, I have taken the old
> interbase one and updated it to cover FB1.5 and my available info on
> SQL99 ( I've added a SQL99 column in addition to the SQL92 one).

> First - since it has had some major work, is there any problem in my
> 'publishing' it - given that the origin was the interbase document -
> which copies other 'standards' documents.

If it's "only" a list of reserved words, I don't see any copyrights
issue. If it also includes text paragraphs written by Borland or
others, we could drop or replace those to be on the safe side.

> Second - If there is not, where can I put this for general use. ( I
> expect that it will need further corrections, but it's accurate to
> the info I have :)

In what form do you have it? Best thing would be to convert it to
DocBook XML and add it to the Firebird manual module. From the XML we
can generate HTML, PDF etc., and place that in the Files section
and/or the project website at SourceForge. I could do the conversion
to DocBook if you like (I suppose it's a small document).


Greetings,
Paul Vinkenoog

[Firebird-docs] Reserved Words

[Lester C. <le...@ls...>]

Not being able to find a complete list, I have taken the old 
interbase one and updated it to cover FB1.5 and my available 
info on SQL99 ( I've added a SQL99 column in addition to the 
SQL92 one).

First - since it has had some major work, is there any 
problem in my 'publishing' it - given that the origin was 
the interbase document - which copies other 'standards' 
documents.

Second - If there is not, where can I put this for general 
use. ( I expect that it will need further corrections, but 
it's accurate to the info I have :) )

-- 
Lester Caine
-----------------------------
L.S.Caine Electronic Services

Re: [Firebird-docs] Build.sh issue

[Paul V. <pa...@vi...>]

Hi all,

>> (...) i try to execute the build.sh script. It returned an error
>> that the java command cannot be found. The JAVA_HOME was correct
>> so i edit the script and added $JAVA_HOME/bin/java blah blah .....
>>
>> The jre is installed in /usr/java/j2re1.4.2_03 dir. Is it my
>> distro (RH8.0 Full Update) or is it a bug ?

> A combination of the two. In some distros, ordinary users (as
> opposed to root) don't have the java bindir in their path by
> default. I've noticed this before; will fix the script soon.

OK, fixed: build.sh now calls java via $JAVA_HOME, just like
build.bat does under Windows.


Greetings,
Paul Vinkenoog

Re: [Firebird-docs] Build.sh issue

[Paul V. <pa...@vi...>]

Hello Dimitris,

> after i installed the java re (rpm) and exported the JAVA_HOME
> variable i try to execute the build.sh script. It returned an error
> that the java command cannot be found. The JAVA_HOME was correct so
> i edit the script and added $JAVA_HOME/bin/java blah blah .....

> The jre is installed in /usr/java/j2re1.4.2_03 dir. Is it my distro
> (RH8.0 Full Update) or is it a bug ?

A combination of the two. In some distros, ordinary users (as opposed
to root) don't have the java bindir in their path by default. I've
noticed this before; will fix the script soon.

In the meantime you did the exact right thing in your own script.


Greetings,
Paul Vinkenoog


PS:
If you *subscribe* to this list at

  http://lists.sourceforge.net/lists/listinfo/firebird-docs

your messages will appear without delay, whether you mail them or post
them through the news interface.