When I install something I want to know the changes [SOLVED]
When I install something I want to know the changes [SOLVED]
I want to be able to install something and track exactly what has been installed so I can use that data to make an sfs file.
What is the easiest way to do this? A script? Comparing current ls to installed? Please advise the best way to accurately record this to eliminate errors.
What is the easiest way to do this? A script? Comparing current ls to installed? Please advise the best way to accurately record this to eliminate errors.
Last edited by steve_s on Thu 26 Aug 2010, 21:41, edited 1 time in total.
You can track operations using installwatch, although the 'sentry' utility included with src2pkg will track even more operations than install. There is a 'tracklist' utility for sentry which parses and simplifies the output from 'sentry' to give just a list of the files, dirs and links created or deleted. It will also report any chown or chmod actions.
Amigo: thank you much for your quick response. I ran installwatch and it made a log, but it is so thorough I can't really grasp it.amigo wrote:You can track operations using installwatch, although the 'sentry' utility included with src2pkg will track even more operations than install. There is a 'tracklist' utility for sentry which parses and simplifies the output from 'sentry' to give just a list of the files, dirs and links created or deleted. It will also report any chown or chmod actions.
Thankfully I had run a full list before my install so I'll just have to go through it manually; tedious but will work.
Thanks again.
As I said, the 'tracklist' tool which comes with src2pkg outputs just the file list. It parses the huge logs created by libsentry(like installwatch logs).
You can get libsentry here:
http://distro.ibiblio.org/pub/linux/dis ... .9.tar.bz2
The tracklist tool is here:
http://distro.ibiblio.org/pub/linux/dis ... /tracklist
You need to compile and install libsentry first. Best tool around for the purpose.
You can get libsentry here:
http://distro.ibiblio.org/pub/linux/dis ... .9.tar.bz2
The tracklist tool is here:
http://distro.ibiblio.org/pub/linux/dis ... /tracklist
You need to compile and install libsentry first. Best tool around for the purpose.
Thanks amigo...good find.amigo wrote:As I said, the 'tracklist' tool which comes with src2pkg outputs just the file list. It parses the huge logs created by libsentry(like installwatch logs).
You can get libsentry here:
http://distro.ibiblio.org/pub/linux/dis ... .9.tar.bz2
The tracklist tool is here:
http://distro.ibiblio.org/pub/linux/dis ... /tracklist
You need to compile and install libsentry first. Best tool around for the purpose.
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
- paulhomebus
- Posts: 120
- Joined: Thu 21 Jan 2010, 23:23
- Location: New Zealand
- Contact:
Just wondering if paco is what you might have wanted....
If you use it when you make install it can be great!
http://users.tpg.com.au/01micko/01mickos_tools.html
Paul
If you use it when you make install it can be great!
http://users.tpg.com.au/01micko/01mickos_tools.html
Paul
runt: just the opposite of that, but thanks; I use that one all the time.
Maybe...I would have to do some trials...i think that or what amigo is talking about would be the best way to go...paulhomebus wrote:Just wondering if paco is what you might have wanted....
If you use it when you make install it can be great!
http://users.tpg.com.au/01micko/01mickos_tools.html
Paul
Hey amigo
thanks for the links to apps on your site you always have good stuff
which amigo has the better solution using the stock puppy
----------------------------------------------------------------------------------------
there is also another way to check to see what will be installed and what will get generated by the install script
**but that only works using pkgtools and slackware packages
I do this on TXZ pup by running a new root
# /root/squashfs-root · this is what you get when you uncompress the sfs
#by default thats the name that is given
this may look odd to someone else that doesnt use pkgtools so I 'll explain what happens for them
basically you are telling the install command to use a new root
so in this case is installing into a folder called
/root/squashfs-root
and then from there you have a real installed program to a folder
making it 100% transparent to see only what was installed
and all the files that get registered in the package management too
this is much better than a chroot because its clean
Joe
I took this a few more steps further and have a GUI for it
thanks for the links to apps on your site you always have good stuff
which amigo has the better solution using the stock puppy
----------------------------------------------------------------------------------------
there is also another way to check to see what will be installed and what will get generated by the install script
**but that only works using pkgtools and slackware packages
I do this on TXZ pup by running a new root
Code: Select all
cd /path-to-folder/PackageName # you have the package or packages you want to install
installpkg -root /root/squashfs-root *.t?z
#by default thats the name that is given
this may look odd to someone else that doesnt use pkgtools so I 'll explain what happens for them
basically you are telling the install command to use a new root
so in this case is installing into a folder called
/root/squashfs-root
and then from there you have a real installed program to a folder
making it 100% transparent to see only what was installed
and all the files that get registered in the package management too
this is much better than a chroot because its clean
Joe
I took this a few more steps further and have a GUI for it
list pet contents
Dear puppians,
Here is a little script I just wrote to show the contents of a pet in a terminal. Just type lspet filename.pet in a console session and you will see something like:
Have fun.
With kind regards,
vovchik
Here is a little script I just wrote to show the contents of a pet in a terminal. Just type lspet filename.pet in a console session and you will see something like:
It should install in /usr/local/bin. I may also do a gui version.root$ [/mnt/hdb6/install]-> lspet pupRadio-0.5.pet
All OK...checking contents....
For some pets (e.g. Wine), this make take a while!
-----------------------------------------------------
Contents of pupRadio-0.5.pet:
-----------------------------------------------------
/usr/share/applications/pupRadio.desktop
/usr/local/pupradio/urls
/usr/local/pupradio/tel-urls
/usr/local/pupradio/config
/usr/local/pupradio/pupradio
/usr/local/pupradio/tel-stations
/usr/local/pupradio/func
/usr/local/pupradio/stations
/usr/local/pupradio/help
/usr/sbin/pupradio
/pinstall.sh
Have fun.
With kind regards,
vovchik
- Attachments
-
- lspet.pet
- (1005 Bytes) Downloaded 482 times
Re: list pet contents
Vovchik,vovchik wrote:Dear puppians,
Here is a little script I just wrote to show the contents of a pet in a terminal.
As usual, a handsome piece of code. Thanks.
I also felt the need some time ago to see what the pet had before installing and for a while I just renamed the .pet extension to tar.gz and opened it with Xarchive until it dawned on me to just change the wrapper file.
Change the file "/usr/local/lib/xarchive/wrappers/tar-wrap.sh" - in the section under "Supported file extentions for tar" add the pet extension.
Code: Select all
GZIP_EXTS="tar.gz tgz pet"
Regards,
s