#36749: kdelibs4 doesn't respect startupitem -----------------------+---------------------- Reporter: mk@… | Owner: nicos@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: kdelibs4 | -----------------------+---------------------- Comment (by pixilla@…): Has duplicate #36751 -- Ticket URL: <https://trac.macports.org/ticket/36749#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS

#36749: kdelibs4 doesn't respect startupitem -----------------------+---------------------- Reporter: mk@… | Owner: nicos@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: kdelibs4 | -----------------------+---------------------- Changes (by mk@…): * status: closed => reopened * resolution: fixed => Comment: Although my configuration file /opt/macports- test/etc/macports/macports.conf defines {{{ startupitem_type none }}} kdelibs4 installs the plist file's link under /Library/LaunchAgents/ {{{ $ ls -1l /Library/LaunchAgents/ lrwxr-xr-x 1 root admin 67 Oct 27 23:31 org.macports.kdecache.plist -> /opt/macports-test/Library/LaunchAgents/org.macports.kdecache.plist }}} '''which is why I think kdelibs4 needs another rework!''' ---- Looking closer at this it seems to me that there are two configuration parameters handling one and the same thing: 1) startupitem_type (which could be set to "none") 2) startupitem.install (which could be set to "no") To me it looks like kdelibs4 just handles case 2, while I am trying to make use of case 1... Why is that or what am I missing? -- Ticket URL: <https://trac.macports.org/ticket/36749#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS

#36749: kdelibs4 doesn't respect startupitem -----------------------+---------------------- Reporter: mk@… | Owner: nicos@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: kdelibs4 | -----------------------+---------------------- Comment (by mk@…): I realized by now that I'd need an even more sophisticated approach to install the launch-agents, since I have minimum 3 MacPorts installations up and running at a time, where 2 of them make use of KDE4 applications (/opt/macports-test and /opt/clean-slate). With the current approach of a single plist file for the lauch-agent it doesn't work. I'd need an agent per installation, i.e. 2 links to the 2 plist files in /Library/LaunchAgents/ {{{ $ ls -1l /Library/LaunchAgents/ lrwxr-xr-x 1 root admin 67 Oct 27 23:31 org.macports .kdecache_opt_macports-test.plist -> /opt/macports- test/Library/LaunchAgents/org.macports.kdecache.plist lrwxr-xr-x 1 root admin 67 Oct 27 23:32 org.macports .kdecache_opt_clean-slate.plist -> /opt/clean- slate/Library/LaunchAgents/org.macports.kdecache.plist }}} -- Ticket URL: <https://trac.macports.org/ticket/36749#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS

#36749: kdelibs4 doesn't respect startupitem -----------------------+---------------------- Reporter: mk@… | Owner: nicos@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: kdelibs4 | -----------------------+---------------------- Comment (by mk@…): In the meantime I've understood that there's more to it than just the cache issue when trying to run several different KDE's on one machine. Of course all the configurations are kept in one place: {{{ ~/Library/Preferences/KDE }}} which doesn't allow in itself the use of more than one KDE installation. :-( -- Ticket URL: <https://trac.macports.org/ticket/36749#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS