Read the system requirements first!
DesktopManagerUniversal.dmg.
Or download a compressed version of it, and then decompress it.DesktopManagerUniversal.dmg.mpkg file./Applications/Utilities.)
The installer will even let you install it onto a volume that
is not the originally selected destination volume.
This is a bug in the installer!
Unless you are using a PPC, you should only install into the
root volume. If you are using an Intel Mac, and know what you
are doing, you may consider installing onto a different volume,
but you should only install onto a volume that is
not mounted with the nosuid option.These instructions were written by someone who knows only enough to be dangerous. Follow them verbatim only if you don't already know how to install from source code. However, if you choose to follow your own installation procedure and you have an Intel Mac, you should make sure to
chmod 2755 DesktopManager.app/Contents/MacOS/DesktopManager
and then
sudo chgrp procmod DesktopManager.app/Contents/MacOS/DesktopManager
If you do not know how to install from source code:
InjectionControl and
DesktopManagerUniversal..tar file, the Terminal instructions
tar -xjvf <filename> (for .tar.bz2)
or tar -xzvf <filename> (for .tar.gz)
will also unpack the package..xcodeproj
file in each project's directory. Once Xcode has loaded the project,
hit Command-B to build.)cd into the directory
InjectionControl-0.2 that was created when you unpacked the
InjectionControl source archive. Make sure you are logged in as
an administrator; if not, type su <admin> where
<admin> is the name of an administrator account,
and type in the
password when prompted. Then type,
sudo cp build/Release/InjectionControl.framework/InjectionControl /Library/Frameworks/InjectionControl.framework/
sudo cp build/Release/InjectionControl.framework/Headers/InjectionControl.h /Library/Frameworks/InjectionControl.framework/Headers/
You have now successfully upgraded InjectionControl. If you are so
inclined, check that no mistake has been made by typing
ls -l build/Release/InjectionControl.framework/Versions/Current/InjectionControl
whereupon you should see
-rwxrwxr-x 1 root wheel 35700 Jul 23 23:27 /Library/Frameworks/InjectionControl.framework/Versions/Current/InjectionControl
If you do not see "root wheel" then execute
sudo chown root:wheel /Library/Frameworks/InjectionControl.framework/InjectionControl
sudo chown root:wheel /Library/Frameworks/InjectionControl.framework/Headers/InjectionControl.h
If the above output did not start with "-rwxrwxr-x" but instead terminated with "---", then execute
sudo chmod 0775 /Library/Frameworks/InjectionControl.framework/InjectionControl
sudo chmod 0644 /Library/Frameworks/InjectionControl.framework/Headers/InjectionControl.h
cd into the directory
DesktopManagerUniversal-0.21, and execute
sudo cp build/Deployment/DesktopManager.app/Contents/MacOS/DesktopManager /Applications/DesktopManager.app/Contents/MacOS/
sudo chmod 2755 /Applications/DesktopManager.app/Contents/MacOS/DesktopManager
sudo chgrp procmod /Applications/DesktopManager.app/Contents/MacOS/DesktopManager
sudo mkbom /Applications/DesktopManager.app /Library/Receipts/DesktopManager-Universal.pkg/Contents/Archive.bom
This has told DesktopManager to run with the group id that owns the file,
and set that group id to procmod. Finally, the default
permissions for DesktopManager were updated.
These instructions were written by someone who knows only enough to be dangerous. Follow them verbatim only if you don't already know how to install from source code. However, if you choose to follow your own installation procedure and you have an Intel Mac, you should make sure to
chmod 2755 DesktopManager.app/Contents/MacOS/DesktopManager
and then
sudo chgrp procmod DesktopManager.app/Contents/MacOS/DesktopManager
If you do not know how to install from source code:
InjectionControl and
DesktopManagerUniversal..tar file, the Terminal instructions
tar -xjvf <filename> (for .tar.bz2)
or tar -xzvf <filename> (for .tar.gz)
will also unpack the package..xcodeproj
file in each project's directory. Once Xcode has loaded the project,
hit Command-B to build.)cd into the directory
InjectionControl-0.2 that was created when you unpacked the
InjectionControl source archive. Make sure you are logged in as
an administrator; if not, type su <admin> where
<admin> is the name of an administrator account,
and type in the
password when prompted. Then type,
sudo cp -r build/Release/InjectionControl.framework /Library/Frameworks/InjectionControl.framework
sudo chown -R root:wheel /Library/Frameworks/InjectionControl.framework
sudo chmod -R go+Xr /Library/Frameworks/InjectionControl.framework
ls -l /Library/Frameworks/InjectionControl.framework/InjectionControl
to check the permissions. For this example, you should see
-rwxrwxr-x 1 root wheel 35700 Jul 23 23:27 /Library/Frameworks/InjectionControl.framework/Versions/Current/InjectionControl
cd into the directory
DesktopManagerUniversal-0.21, and execute
sudo cp -r build/Deployment/DesktopManager.app /Applications/DesktopManager.app
sudo chmod -R go+Xr /Applications/DesktopManager.app
sudo chmod 2755 /Applications/DesktopManager.app/Contents/MacOS/DesktopManager
sudo chgrp procmod /Applications/DesktopManager.app/Contents/MacOS/DesktopManager
This has told DesktopManager to run with the group id that owns the file,
and set that group id to procmod.
/Library/Receipt/ entries. This is because I do not know
how to make the packages therein, only the .bom files
themselves. You are on your own...
To uninstall DesktopManager, simply use Finder to
drag DesktopManager from the installation directory to the trash.
That's it! If you are feeling pedantic, you might also delete
(Intel) /Library/Receipts/DesktopManager-Universal.pkg
or (PPC) /Library/Receipts/DesktopManager-PPC.pkg.
You will need an administrator password.
If you want to also uninstall InjectionControl, please reconsider.
The InjectionControl framework is not taking up much space on your harddrive,
but it is embedded in there, and is not affecting performance because it
is only loaded when required by another application (such as DesktopManager).
Also, I do not know enough about frameworks to know if MacOS knows
of the existence of InjectionControl in any other way than its simple
presence in the /Library/Frameworks/ folder, but if it does,
then simply deleting it
could cause problems in the future.
However, if you insist, you can simply delete the folder
/Library/Frameworks/InjectionControl.framework.
Finder will ask you for an administrator's password.
You can then, if you wish, also delete
/Library/Receipts/InjectionControl.pkg.
-
This page was last modified 2006-08-13 07:48 PDT.
©2006 jeremy.smallinfinity.net. The program and its source code has various additional (open source) copyrights associated with it, as detailed in the source code.