That's great but what about all the associated files and dependencies. Are they left behind or do they get deleted too.

Example: If you search for 'abiword', everything with 'abiword' in the name gets removed - including any files (of any name) that are inside any folders that match 'abiword'.

Smokey01 wrote:

This didn't work for me. I tried to remove abiword but it was still there on the remaster

This removes most stuff, but I was gonna do the same as Moo - add pets to a directory and they get removed..
But this requires users to have the pet files of the stuff they want deleted, and it's a fair bit slower..

smokey01 wrote:

Yes and means you need a lot of additional pets that you really are not going to use except as a reference to delete original.

Finding these pets, and gettting the correct versions may be a problem..
And it still doesnt solve the dependencies 'issue'..

smokey01 wrote:

True

About this issue - there is no way a user can safely remove the dependencies of any app, without knowing the name of those libs and which other apps share them..

There is no way to automatically and safely remove all libs, if the user doesn't know what can be removed safely..

smokey01 wrote:

Agree

So, there is no real value in having or building a list of dependencies for apps, because users will still need to know which are safe to remove.

Users cannot escape the need for this knowledge - so putting the libs you want removed in the list is as easy as it can get..

There is a solution. puppy needs a database of installed software that can be safety removed. The database needs to include all files and dependencies. It also needs to be able to identify shared files and dependencies. This should be part of the basic puppy structure. By having something like this it would be very simple to add and remove applications safely. It could be achieved with something as simple as a gui with check boxes. Untick the check box and the package is deleted. Check it and the package is downloaded and installed. Ok, nothing is ever that simple but by having a database or reference file for all removable applications would be very useful._________________Software <-> Distros <-> Tips <-> Newsletters

Iguleder unfortunately my skills are not that advanced. If they were I would do it and believe me I have tried. Time is my biggest killer. Although I'm getting on a little I still work 10 hour days.

I think the easiest way might be to build a very bare bones pup with woof then add only the packages you want. The problem with this is all the installed packages end up in the save file and not the main sfs file. I guess it would be possible to create a special sfs file which could be loaded with boot manager. Once all the bugs were sorted then use either moo or woofy to consolidate all the files into the one sfs. Would this work?

There are so many different puppy distos and many of them are great. I continually hear people say, If I could just get rid of these few applications that I never use and add these it would be perfect. The adding part is easy and the removing of added applications is also quite easy with PPM. It's getting rid of the original files that is the issue for most people. Woof is great and very useful but beyond the grasp of many.

Keeping the mind active and having these conversations certainly prevents the brain from turning to mush.

Please don't think because I make suggestions I am being critical because that's certainly not my intent. I have worked with many in the forums to solved a great number of problems. Helping people is what I enjoy.

I wrote a tool that downloads all PETs used to build a certain Puppy ... it also has Slackware support for spup (let me tell you a secret: I'm trying to build my own Woof-like thing ). I'm currently trying to make a local copy of all 4.3.1 PETs ... I want to try to strip it down with Moo to produce a true barebones 4.3.1.

Regarding the barebones Puppy many people want, it's quite hard to achieve that, dependencies are quite complicated and most of the space in the main SFS is taken by massive amounts libraries and important things like kernel modules._________________My homepageMy GitHub profile

Talking about installed files, have you looked in Barry's latest spup. In the root/.packages there is a folder with all the installed packages and where the dependencies are.
I think this is what you may be looking for.

Talking about installed files, have you looked in Barry's latest spup. In the root/.packages there is a folder with all the installed packages and where the dependencies are.
I think this is what you may be looking for.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum