[CalendarServer] #317: System install (run's -i option) ambiguities
#317: System install (run's -i option) ambiguities -----------------------------------+---------------------------------------- Reporter: AxelLuttgens@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | -----------------------------------+---------------------------------------- I don't know how to classify this one. It may just prove to be strictly cosmetic, or contrary wise reveal some glitches in the logics of the run script; if the latter, this ticket could then be related to ticket #316. A system install seems to know about /System/Library and /Library. Those directories are typical of Mac OS X. But then, why does such an install put things into /usr/local/bin as well, instead of /usr/sbin or /usr/share for example? The installation location for caldavd.plist is rather surprising: /System/Library/Frameworks/Python.framework/Versions/2.5/caldavd: caldavd.plist... If a system install insists on putting things under /usr/local/bin, why does the default config (as of config.py) still consider that twistd's path is /usr/share/caldavd/bin/twistd? In the same vein, and this seems to be directly related to #316, a PATH is set to a non existing /System/Library/Frameworks/Python.framework/Versions/2.5/bin... As a result, the default layout yielded by run's -i option really appears as an hybrid install: many similarities with a home install and some reminiscences of what may be observed on Mac OS X Server. More generally, the rationale underlying the -i and -I options don't appear clearly. Unless some bug (typo) is at work. Unless I just don't understand those matters... TIA, Axel -- Ticket URL: <http://trac.calendarserver.org/ticket/317> CalendarServer </> HTTP/WebDAV/CalDAV Server
#317: System install (run's -i option) ambiguities -----------------------------------+---------------------------------------- Reporter: AxelLuttgens@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | -----------------------------------+---------------------------------------- Comment(by wsanchez@…): `/usr/bin` and `/usr/share` are for operating system components. Things that are added by someone other than the OS vendor should live in `/usr/local`. See the hier(7) man page, look for "executables, libraries, etc. not included by the basic operating system". We probably shouldn't be installing into `/System` for the same reasons, though. `/Library` is OK. We probably should also use a different path if we aren't on Mac OS for stuff in `/Library`, probably `/var/spool`. As to "home install" vs "system install": that's kinda of a weird python distutils thing; a home install is for a user-specific setup (ie. you don't have root access, or don't want to install system-wide). If you are creating packages for an installer, you want a system install into a temp dir (eg. `/tmp/dst`) and pack up its contents for overlaying onto a system. -- Ticket URL: <http://trac.calendarserver.org/ticket/317#comment:1> CalendarServer </> HTTP/WebDAV/CalDAV Server
#317: System install (run's -i option) ambiguities -----------------------------------+---------------------------------------- Reporter: AxelLuttgens@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 3: Important | Milestone: Later Component: Calendar Server | Severity: Other Keywords: | -----------------------------------+---------------------------------------- Changes (by wsanchez@…): * priority: 5: Not set => 3: Important * milestone: => Later -- Ticket URL: <http://trac.calendarserver.org/ticket/317#comment:2> CalendarServer </> HTTP/WebDAV/CalDAV Server
#317: System install (run's -i option) ambiguities -----------------------------------+---------------------------------------- Reporter: AxelLuttgens@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 3: Important | Milestone: Later Component: Calendar Server | Severity: Other Keywords: | -----------------------------------+---------------------------------------- Comment(by alexis@…): This desperately needs just a little bit of documentation. It would be sufficient to say "This type of install puts files in the following directories: ...", and it would be extra-helpful to say what the target is supposed to be for. Since I don't want this on my Macs, I am going to have to move stuff into /var/lib, /var/spool, and /etc. Not having docs on what parts of your hierarchy are what makes this more challenging to get right, though I think it'll be alright - I'll try it in the next few days. -- Ticket URL: <http://trac.calendarserver.org/ticket/317#comment:3> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server
participants (2)
-
Calendar and Contacts Server
-
CalendarServer