What about saving it as a lib and creating a sim-link to it named
/usr/bin/saxon also?
:)
- Original Message -
From: "Mark Johnson" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, June 26, 2001 1:53 AM
Subject: java packaging questions
> Hi All,
>
> I package some of the DocBook XML stuff and wa
What about saving it as a lib and creating a sim-link to it named
/usr/bin/saxon also?
:)
- Original Message -
From: "Mark Johnson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 26, 2001 1:53 AM
Subject: java packaging questions
> Hi All,
>
> I package some of the DocB
On Monday 25 June 2001 15:53, Mark Johnson wrote:
> Hi All,
>
> I package some of the DocBook XML stuff and want to package some java
> xslt processing tools as well, but I'm not too clear on a few policy
> points. Any help/suggestions would be much appreciated. Here goes:
>
> 1. Package naming, li
* Mark Johnson
|I have similar questions for other packages I'd like to upload. The
|arbortext catalog classes (and related extensions) that provide
|catalog support for saxon and XT are an example. I could package
|the base classes as "lib-arbortext-java", the saxon extensions as
On Monday 25 June 2001 15:53, Mark Johnson wrote:
> Hi All,
>
> I package some of the DocBook XML stuff and want to package some java
> xslt processing tools as well, but I'm not too clear on a few policy
> points. Any help/suggestions would be much appreciated. Here goes:
>
> 1. Package naming, l
* Mark Johnson
|I have similar questions for other packages I'd like to upload. The
|arbortext catalog classes (and related extensions) that provide
|catalog support for saxon and XT are an example. I could package
|the base classes as "lib-arbortext-java", the saxon extensions a
6 matches
Mail list logo
