Page 1 of 2
When I install something I want to know the changes [SOLVED]
Posted: Thu 26 Aug 2010, 15:12
by steve_s
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.
Posted: Thu 26 Aug 2010, 17:13
by amigo
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.
Posted: Thu 26 Aug 2010, 18:51
by steve_s
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.
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.
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.
Posted: Thu 26 Aug 2010, 19:46
by Flash
Could
Menu -> Utility -> Xdelta file difference manager be used for what you want to do? I haven't tried it so I don't know anything about it other than the name.
Posted: Thu 26 Aug 2010, 19:56
by jemimah
Posted: Thu 26 Aug 2010, 20:03
by Flash
Barry creates delta files for updating developmental Puppys without downloading (and uploading) the entire iso. He must have some way to find the difference.
Posted: Thu 26 Aug 2010, 21:22
by jemimah
Well the binary difference is not that useful for remastering. If you want to know what files changed and how you can't use Xdelta.
Posted: Thu 26 Aug 2010, 21:27
by steve_s
thanks all...great ideas....don't know which is best...
Unfortunately I've already installed it then went through the lists manually...what's worse is it's a big program installed in wine...I have to take a few minutes and gather my brains back into my skull...I should have waited for y'all...ugh.
Posted: Fri 27 Aug 2010, 07:10
by amigo
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.
Posted: Fri 27 Aug 2010, 15:51
by steve_s
Thanks amigo...good find.
Posted: Fri 27 Aug 2010, 15:57
by technosaurus
also ... for most files you can also look in /root/.packages/<name_of_pet> .files
Posted: Fri 27 Aug 2010, 16:01
by steve_s
technosaurus wrote:also ... for most files you can also look in /root/.packages/<name_of_pet> .files
Thanks for that, techno, but this was a wine file and it doesn't list those there, does it? But thanks for the post.
Posted: Fri 27 Aug 2010, 21:49
by runtt21
This may not be what you are asking for but I like to take .pets apart it see what is included.
For example say you have a RUNTT.pet move it some place where you can work on it and run ...
pet2tgz RUNTT.pet
That will turn it into a .tar.gz that you can unpack and snoop through .
Posted: Fri 27 Aug 2010, 22:22
by paulhomebus
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
Posted: Fri 27 Aug 2010, 22:34
by steve_s
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...
Posted: Sat 28 Aug 2010, 03:34
by big_bass
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
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
# /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
Posted: Sat 28 Aug 2010, 08:57
by amigo
Tracklist, when used with sentry, will track file, etc creation by any command. So, if you are running an installer script, or the command 'make install' or whatever, it will tell what happens when the command is run.
Posted: Sun 29 Aug 2010, 13:04
by steve_s
Thanks again, all! Great stuff!
list pet contents
Posted: Sun 29 Aug 2010, 21:08
by vovchik
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:
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
It should install in /usr/local/bin. I may also do a gui version.
Have fun.
With kind regards,
vovchik
Re: list pet contents
Posted: Mon 30 Aug 2010, 03:15
by seaside
vovchik wrote:Dear puppians,
Here is a little script I just wrote to show the contents of a pet in a terminal.
Vovchik,
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.
Now a right click with Xarchive opens the pet file and you have all the information and the possibility to extract any individual file for a further look.
Regards,
s