hugin-devs team mailing list archive

[Yuv <789436@xxxxxxxxxxxxxxxxxx>]

For plugins this has been solved - system-wide plugins are installed
with Hugin's data directory; for user-specific plugins the user has a
preference setting.

For system-wide standalone scripts the proper location is in an
executable path (e.g. /usr/bin or /usr/local/bin on Linux/BSD machines).
User-specific scripts can go anywhere the user wants in his/her home
folder. Currently we don't have standalone scripts.

** Changed in: hugin
       Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/789436

Title:
  2011.2: Python scripts location

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  * CLI scripts should be installed in the executable path and on Linux/Unix system receive executable permission.
  * Plugins should be installed in a known location to facilitate starting of the execute script dialog.

  There are four categories of scripts, three of which need a specified
  folder/location:

  1* HPI global

  system-wide plugins that are shipped with Hugin by default and are
  considered core functionality.

  2* HPI local

  user-specific plugins.

  3* HSI global

  system-wide python scripts that represent new CLI commands that are
  considered core functionality.

  4* HSI local

  location left up to the user.  user can write/run their own HSI
  scripts with `import hsi` anywhere they have write access in the file
  system.

   Prior to release we need to decide and implement:
  - where are those script installed (plus variations on the different platforms)?
  - are these location hard-coded or left to the user's preference?

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/789436/+subscriptions