Wiki     Timeline     Roadmap     Browse Source     View Tickets     New Ticket     Search

Ticket #390 (closed Enhancement: Behaves correctly)

Opened 6 years ago

Last modified 4 years ago

$PYTHONPATH should be configured automatically by the 'run' script when used with -i (install)

Reported by: s.adam@… Owned by: wsanchez@…
Priority: 4: Nice to have Milestone:
Component: Calendar Server Severity: Other
Keywords: Cc:


After unpacking & building calendarserver-2.4, I installed it to my machine via: DESTDIR=/opt/CalendarServer ./run -s -i "$DESTDIR"

The installation itself works, however the 'run' script does not set $PYTHONPATH in the installed binaries as it does when running from the source directory. This results in Python errors when attempting to start the server from the new installation directory.

This problem can be worked around by manually wrapping the caldavd binary in a shell script and setting PYTHONPATH="$DESTDIR/usr/lib/python2.6/site-packages:$DESTDIR/usr/lib64/python2.6/site-packages".

Note - I'm on an x86_64 system... On x86 systems, only PYTHONPATH="$DESTDIR/usr/lib/python2.6/site-packages" would be required.

Change History

comment:1 Changed 5 years ago by wsanchez@…

  • Status changed from new to closed
  • Resolution set to Behaves correctly

The -i flag sets a location to install into such that you can create a package from the data in that location, where that location is equivalent to /. It passes --root to So this behaves as expected.

It sounds like what you want is --prefix=/opt/CalendarServer. If you want to get custom with the installation, then you need to build and install each dependency yourself, then run our directly.

Note: See TracTickets for help on using tickets.