Page 1 of 1

GUI dependency lister script

Posted: Wed 04 Feb 2009, 18:12
by big_bass
I wrote a simple GUI script that is platform independent

I use this on puppy and slackware

simple
just down load it click on it it will unzip
put it "wherever you want " it will work
or drop in in the the root speed_build folder if you like

*note: for slackers slackware needs gxmessage installed and xdialog

this is a great tool for packagers and users

users can report easily whats missing
to the packagers without knowing what to do
they just zip and send the text file attached in the forum post :D


and we have some standard order
that should also be included in each package made


run this on pre installed packages or alien packages too

a text file is auto generated and saved in
/root/speed_build/dependencies ##everything is saved here

this is just one script from my GUI front end package management system

the first few of you *the quick ones *who downloaded change the permissions to executable I re uploaded it with that fixed

big_bass

Posted: Wed 04 Feb 2009, 19:11
by sunburnt
Good work big_bass, you've made the front end for a "automated dependency downloader & installer".
I was working on such a utility for Puppy about 2 years ago.

All that's needed is code that uses wget to download the missing dependencies from a web site.
The web site's URL should be gotten from a solid web site so the actual dependency site's URL can change.
Code's also needed to install the downloaded dependencies into Puppy & then run another check to be sure.

This utility could really be a hot number for Puppy!

Posted: Fri 06 Feb 2009, 01:47
by big_bass
sunburnt
I am working on a new depends file format for packages to simplify package management

like the slack-required
but more flexible

so the packager includes an auto generated text file showing all the libs
this will help out with deb and slackware or other packages greatly

you can easily verify your package before uploading also
and see what and where each lib was linked to on the host machine
for debugging if needed

any fully automated package management is doomed
due to the fact that every puppy version is truly unique
*note if there were only official packages
it could be possible but you stop development
from so many people



instead of changing puppy .....
it would be better to adapt
to some organized standard
of knowing what each package depends on
clearly listed in a text file
not to much to ask for
and I even provided an easy way to auto generate the file
and I have bulk scripts also to do several hundred
quickly and painlessly if needed

this came about after building a puppy package building envirornment
on my slackware box and building a front end for the slackware package tools
then compiling and building slackware packages on puppy

so it was a process
and to sort out everything easily
between deb /slackware/source compiled packages and puppy
this was what works for me


I welcome all of your suggestions and hope you can help out
since you said that you wanted to that a few years ago
now is a good time

big_bass

Posted: Thu 12 Feb 2009, 15:50
by big_bass
here's one more script
for advanced users

this is a dragNdrop
any BIN

from /bin /usr/bin /sbin /usr/sbin
usr/local/bin



onto the script to see the dependencies
this is much faster than typing

you get the idea...

super tools
for package building

I also have one for lib dependencies
I'll upload if anyone requests it

big_bass

Posted: Thu 12 Feb 2009, 16:57
by ttuuxxx
wow thats a handy tool, great job :)
ttuuxxx

Posted: Thu 19 Feb 2009, 10:37
by aragon
hi big_bass,

i wonder if it would be possible to have a 'reverse-dependency-checker'?

e.g. submit 'libsamplerate' and the tool searches for apps that use this library.

aragon

Posted: Thu 19 Feb 2009, 17:05
by big_bass
aragon wrote:hi big_bass,

i wonder if it would be possible to have a 'reverse-dependency-checker'?

e.g. submit 'libsamplerate' and the tool searches for apps that use this library.

aragon
here is an example from slackware 12.1 libsamplerate
flac >= 1.2.1-i486-1
glibc-solibs >= 2.7-i486-10
libogg >= 1.1.3-i486-2
libsndfile >= 1.0.17-i486-1sl


now the tricky part here is is what version was your build
compiled against ? what puppy version
are you using ? what other apps requires it ?

did you mix and match dependencies or did you use full packages ?

I used libsamplerate in a few packages you need to be careful for conflicts
with other packages that use it too


puppy is too mixed and matched
with different packages at the present state
for many reasons

I would like to see some order
when it comes to dependencies
and this was the reason for a dependency list from the host machine
and the new target host machine so that you verify the package integrity


big_bass

Posted: Thu 19 Feb 2009, 17:10
by sunburnt
I don't see that an automated installer isn't feasable.
I've used many Puppy variants & even NathanF's highly modified Puppy worked with all the files from Debian.
I've yet to find a package or library at Debian that didn't work with Puppy.

Posted: Thu 19 Feb 2009, 17:21
by big_bass
sunburnt wrote:I don't see that an automated installer isn't feasable.
I've used many Puppy variants & even NathanF's highly modified Puppy worked with all the files from Debian.
I've yet to find a package or library at Debian that didn't work with Puppy.
never said it couldn't be done
just the present state of puppy doesnt lend itself to it version 4.12 and lower

now with woof in the making using more packages from a
lets say slackware ,debian, arch

having version numbering and dependency info at hand
there is a greater degree of that becoming a reality

so I am for it but many steps need to be taken first
to prepare the way for it to come

even slackware can be broken with tools such as gslapt
and a lot of pre planning and testing went into it

sunburnt I would be happy improving the current state to any degree
and trying new ideas if you want to take steps to improve things
I am all for it and open ears

big_bass

Posted: Thu 19 Feb 2009, 18:20
by aragon
hi big_bass,

i think there was a little misunderstanding, libsamplerate was just an example.

what i want to know is, can i delete a special library, as i don't know which programm is using this lib?

so the input would be

Code: Select all

libsamplerate
the output could be as an example

Code: Select all

- mhwaveedit
- audacious
or

Code: Select all

No application is actually using 'libsamplerate'!
aragon

Posted: Fri 20 Feb 2009, 15:39
by big_bass
aragon
what i want to know is, can i delete a special library, as i don't know which program is using this lib?

so the input would be

the closest I can do on puppy is this
show you the current on packages then look for the +
symbol

those are apps/libs are linked with petget

What you want requires reading a pre-made package.txt with all the info
setup in advanced and we are not there yet

but anyway I hope this basic script helps
it should work on all puppy versions
not pretty but gets the job done

an added feature here you can safely select text from inside the dialog box then paste to another location outside the dialog box
example create a list for easy reading later

without fear of messing up your original official packages file


big_bass