Hi Dimitar, Thank you very much for this long and very clear message. I will see a solution with the departement who installs the package and adapt it to our needs.
Thanks
Marc
Le 09/09/2014 23:20, Dimitar Popov a écrit :
On Monday 08 September 2014 08:52:41 Marc wrote:
Hi Dimitar,
Thank for answer
When I install the jar version I have a 'basexserver' script in the 'bin'
directory and a 'lib' directory. But when I said to the guys who does the
installation on the server with the redhat package, the 'basexserver'
script isn't the same and I don't have the 'lib' directory, I don't
know if
it's a problem of the package or of the installation procedure.
I hope that explains you a little more.
Regards,
Marc
Hi Mark,
We must comply to certain rules, when we prepare packages for the different Linux distributions. One of these rules is that we have to install the BaseX files to perdefined directories. The redhat package will install the following files:
/usr
├── bin
│ ├── basex
│ ├── basexclient
│ ├── basexgui
│ ├── basexserver
│ └── basexserverstop
└── share
├── applications
│ └── basex.desktop
├── icons
│ └── hicolor
│ ├── 128x128
│ │ └── apps
│ │ └── basex.png
│ ├── 16x16
│ │ └── apps
│ │ └── basex.png
│ ├── 256x256
│ │ └── apps
│ │ └── basex.png
│ ├── 32x32
│ │ └── apps
│ │ └── basex.png
│ ├── 48x48
│ │ └── apps
│ │ └── basex.png
│ ├── 512x512
│ │ └── apps
│ │ └── basex.png
│ ├── 64x64
│ │ └── apps
│ │ └── basex.png
│ └── scalable
│ └── apps
│ └── basex.svg
├── java
│ └── basex.jar
└── man
└── man1
├── basex.1.gz
├── basexclient.1.gz
├── basexgui.1.gz
└── basexserver.1.gz
Additionally, we cannot include pre-compiled binaries in our packages - all binaries in the package must be generated from sources. This is why the lib directory is not available. This is also the reason why we don't ship basex-api (which includes the BaseX HTTP server, and bindings to different languages, and APIs) with any linux package - these features require libraries which are not always available in every linux distribution and some are even closed source (e.g. basex-xqj).
The basexserver script is not the same as the one we provide with the zip archive, because it is generated with the help of JPackage. This is a standard way to generate startup scripts in different linux distributions. The advantage of using JPackage is that optional libraries will be automatically used by basex if they are installed in the system (e.g. jline for history in the basex comman-line interfaces, or tagsoup).
I hope this answers your questions. I'll be happy to provide you with more information.
Best regards,
Dimitar