Project

General

Profile

Actions

Feature #319

closed

Determine how appion/bin programs should be used

Added by Neil Voss over 14 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Amber Herold
Category:
-
Target version:
Start date:
04/02/2010
Due date:
% Done:

100%

Estimated time:

Description

Determine how appion/bin programs should be used

Currently, we have several program that need to be executed in the appion/bin folder

There are three ways to properly install appionlib:

  1. Tell users to put appion/bin folder directly in PATH evironmental variable
  2. Tell users to put appion/bin/*.py folder directly in /usr/local/bin or /usr/bin
  3. Put a symbolic link to the appion/bin/appion script into /usr/local/bin or /usr/bin and then use the appion script to launch all programs, e.g.
    appion makestack2.py --option1 --option1
    

If we go with option #3, then we should change the webpages to use this script

a typical site-packages folder is: /usr/lib/python2.6/site-packages/


Related issues 6 (2 open4 closed)

Related to Appion - Feature #318: Determine how appionlib folder should be installedClosedAmber Herold04/02/2010

Actions
Related to Appion - Feature #662: Pass all command line results from "Just Show Command" to a common functionClosedAmber Herold06/15/2010

Actions
Related to Appion - Feature #661: Add use_appion wrapper and path to appion wrapper to config.phpClosedChristopher Irving06/15/2010

Actions
Related to Appion - Task #675: Document appion wrapper config in install guideNew06/16/2010

Actions
Related to Appion - Feature #676: Instead of installing appion scripts into bin, use the appion wrapperNew06/16/2010

Actions
Blocks Appion - Feature #320: Make installation of pyappion easierClosedAmber Herold04/02/2010

Actions
Actions

Also available in: Atom PDF