WDef

Group: Members
Posts: 798
Joined: Sep. 2005 |
 |
Posted: Sep. 05 2006,23:45 |
 |
Just FYI, to build pseudo debs packages effortlessly (not that I suggest this for gcc):
checkinstall.dsl from the repo.
Tries to make a deb, rpm or slackware package from most install processes. Do:
Code Sample | # checkinstall -D tar -C/ -zxvf someextension.dsl |
and follow the prompts. The only important menu item is [2] = package title.
It requires the dpkg, gnu-utils and gcc extensions as dependencies - I neglected to mention that in the info file. Sorry.
For people with traditional hard drive installs, there is a very good reason to make a pseudo deb package, especially when compiling, or unpacking some binary tarball: the package manager will be aware of it after installing, which means a clean uninstall (that may run into glitches if the extension overwrites system files - look at that first).
|