Posts

Showing posts with the label dpkg

How to explode DEBian package file.

I wrote this because My senior need to get uwsgi ( newer version ) than registered in precise repos. At that time we found great guy Chris Lea ( https://launchpad.net/~chris-lea/+archive/uwsgi ), thank chris :). But if we don't found him. I plan to explode current debian version from precise repos to see the structure and all script. Here is how to do that Get one (deb pkg) i assume uwsgi-current.deb 1. The first way Using dpkg-deb -x , you will get inside debian structure. > dpkg-deb -x uwsgi-current.deb [target-folder] Using dpkg-deb --control , you will get control files, debian control scripts. > dpkg-deb --control uwsgi-current.deb [target-folder] /DEBIAN 2. The second way,  the first way can be done in short time in  > dpkg-deb -R uwsgi-current.deb [target-folder]

About DPKG

ref  http://www.cyberciti.biz/howto/question/linux/dpkg-cheat-sheet.php ref  http://linuxprograms.wordpress.com/2010/05/14/dpkg-tutorial/ Very thank for Owners of 2 links above. The first column corresponds to the status of a package. How to interpret this status. Status of every package is represented by  three characters xxx Let’s explore each of the character signify. First character : The possible value for the first character. The first character signifies the desired state, like we (or some user) is marking the package for installation u: Unknown (an unknown state) i: Install (marked for installation) r: Remove (marked for removal) p: Purge (marked for purging) h: Hold Second Character : The second character signifies the current state, whether it is installed or not. The possible values are n: Not- The package is not installed i: Inst – The package is successfully installed c: Cfg-files – Configuration files are present u: Unpacked- The pac...