[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[aperi-dev] Proposed Changes to the Configure Aperi Script to handle 3rd Party Code
|
Aperi-dev,
I would like to propose the following changes to the configure Aperi script, cfgaperi. The goal is to reduce the amount of manual configuration required to use the binary distribution.
Background:
We are not able to ship 3rd party software with our binary distribution for legal reasons.
Proposed Solution:
The cfgaperi script will do the following:
0. Load a list of 3rd party software from a file.
1. Display the list of the 3rd party software required by Aperi.
2. Prompt the user if they would like to have the cfgaperi script download and configure the 3rd party software automatically.
3. Select a mirror site for the download, if applicable.
'easy' mode: The first available mirror will be selected for the download (no user input).
non-'easy' mode: Display a list of available mirrors and ask the user to select a mirror from the list.
4. Download 3rd party plugins directly to the 'plugins' directory.
Note: Plugins will not be downloaded if they are already present.
5. Download jars directly to the 'lib' directory.
Notes:
1. If the required jars are contained in a zip file, then the zip will be downloaded to a temporary directory the jars will be extracted to the 'lib' directory
2. The jar will not be downloaded if it's already present.
Limitations:
1. Only http downloads will be supported.
2. These changes will NOT be able to handle some of the 3rd party dependancies. The Java help and the J2EE jar files cannot be downloaded automatically because they are behind a restrictive click-through license.
-- Craig
________________________________________________________________
Craig Laverone | 408-284-4897 | laverone@xxxxxxxxxx | Aperi Development
