1. I still need to be sure of the correct method used in 4.2 and under (Unleashed puppies) to set distro name?

2. I want to be able to change sfs prefix, but methods seem to differ in <4.2 and 4.3>

The sfs prefix in the 4.2 init script is hardcoded to 'pup_', is this the same in all Puppies?
Or is the prefix value (in the init script) now taken from DISTRO_SPECS, as your code suggests?

About version numbers:

Actually, in Woofy, I will simply leave the version number unchanged from the base..
I don't think its right to change the version number - they are not new versions built from nothing, only puplets..
People could remaster a 4.2 iso, and call it 431, 433, or even 503, just to be first..
I dont want to contribute to even more confusing puppy version numbers..

Finally..

I'm 99% sure that my defaults-changer will just need a prefix added to the file paths to work on an extracted sfs...
I'm doing it now.. At least that should be nice and quick _________________Akita Linux, VLC-GTK, Pup Search, Pup File Search

I think 2.14x has DISTRO_SPECS because ttuxxx took many scripts from Woof ... they determine the version number and distro name according to that file.

I've noticed some stuff use /etc/puppyversion ... like pwidgets. I added that to Moo already.

Try to take a look in the 4.2.1 init scripts (in /etc/rc.d) and see how they detect the distro name and version. Maybe it's fixed, so you'll need some sed work._________________My homepageMy GitHub profile

I'm currently trying to integrate Moo with Woof, find a way to auto-download Woof and steal the rootfs-skeleton thing from it. That can also solve the splash screen problem, because Woof generates it. The problem is applying the distro details ... the DISTRO_SPECS file is not enough.

If I get anything to work, I'll post it.

Also, I had a funny idea, a tool that gets a list of PETs and makes a Puppy from them. Just takes a pets list, then downloads them and Woof, trims the packages and viola, a new Puppy. Sort of a combination between Unleashed and Woof _________________My homepageMy GitHub profile

I certainly do, i was just waiting for you two devs to reach a level when you were reasonably happy with your efforts.
Keep on working on it please and it could be one of the best projects for woof builds.

I certainly do, i was just waiting for you two devs to reach a level when you were reasonably happy with your efforts.

So far, I am very happy with Woofy (especially with lguleders additions), as it all works perfectly and is very simple to use...

I'm actually now using a 'woofylet' as my default OS.. Very happy with it.

I just wanna add a few features - without complicating the Woofy remaster process..
Woofy currently allows a '1 click' remaster - I'd like to keep this feature

This way, even new users can simply add packages and click 'Go'..

Changing the actual distro name is not that important to me - as it's pretty much hidden from the user, anyway..
I may leave it.. Changing wallpapers, gtk themes and splash images have more effect..

But adding a few bugfixes 'on the fly' would be nice.. I'll look into it..
I may need a list of bugfix suggestions (and help!) from people..

And I would love to let users choose a new splash screen, cos it makes a big difference to puplets...
I repeatedly find myself missing the files required to check it out...
But couldn't an image just be replaced?

tubby wrote:

Keep on working on it please and it could be one of the best projects for woof builds.

Moo or Woofy?? Cos for Woofy, I'm not gonna add any features which will only work for Woof built puppies..
I want Woofy to be VERY simple to use...
So I need all features to work as expected, no matter what ISO is chosen.

Perhaps Moo will be more suited to more advanced users, who want to change specific 'Woof' features.

You're right, I'll open a new thread for Moo, sort of a "development version" of Woofy for more advanced users

This way you can work on Woofy and I on Moo in parallel, share ideas and features ... could be great. I find this quite fun, actually ... I'm looking forward to improve Woofy. Moo is just my "plaything" (quote of Barry ), I just don't like working with alien code, so I wrote my own remaster tool from scratch to help you with Woofy, but now it's so fun I can't resist the urge to make it full-featured

By the way, I'm currently working on the skeleton updation code ... would you like me to write some code that makes a non-Woof Puppy a Woof-Puppy? I mean, puts all the Woof stuff, including the new PPM and all Puppy wizards?

Guys here are a few ideas for you to think about. You may have already implemented some of them.

The thing that I find really annoying is dependency control. Ok let me provide a working example.

I take a perfectly good distro and install a new software package. The files that are installed are stored in a package file so they can be uninstalled later with PPM if you decide to uninstall the package. The problem is some dependencies are required by a number of packages. Now PPM is smart enough not to delete all files automatically and you have to manually delete some if you want. Most of the time people don't bother in case they delete something required and break another package. I'm not sure how this is done but I guess it looks at the package install list.

Now what would be really nice is a way of checking to see if the dependency already exists. If it does do not install it again, maybe ask if it is a later version. If we had something like this then all packages could contain all dependencies and the missing dependency problem would disappear, unfortunately the packages will be bigger than necessary.

Another method might be to do a test install to see what dependencies are missing/required before installation. Sort of similar to check dependencies before installation instead of after.

One last thing. It would be nice to have a package list of all software in puppy that could be safely removed. This would allow you to make your own bare bones puppy then install what you like. This would be a great enhancement to woofy.

I already have many fixes for Woofy, sc0ttman. Here's my 005.
- Use of mktemp for the creation of temporary files and working directories
- Much better error detection
- Way better validation of the selected options
- Clean up code in case the remastering fails

Now it's much better and safer. Also more user friendly, you should add those to Woofy.

The next Moo will have its own thread, since 006 is going to mess with Woof itself, not very useful for Woofy, although I'm pretty sure making Woofy apply all the Woof stuff to an Unleashed Puppy is a nice trick

msgbox "Your puplet is $pupletName ${pupletVersion:0:1}.${pupletVersion:1:1}.${pupletVersion:2:1}; the remastered ISO will be $isoDirectory/$pupletPrefix-$pupletVersion.iso." "The remastering process will begin now. It may take time; you will see a message when it is over." "Press \"OK\" to continue."

mount_iso

if [ "$(mount | grep "on $isoMountPoint")" != "" ]; then

extract_iso

if [ "`ls $isoWorkingDirectory`" != "" ]; then

extract_sfs

if [ "`ls $sfsWorkingDirectory`" != "" ]; then

unmount_iso

if [ "$(mount | grep "on $isoMountPoint")" = "" ]; then

add_pets
add_stuff
last_minute
select_artwork
create_initramfs

if [ -f "$isoWorkingDirectory/initrd.gz" ]; then

create_sfs

if [ -f "$isoWorkingDirectory/$pupletPrefix-$pupletVersion.sfs" ]; then

<entry accept="directory" tooltip-text="This is a working directory where Moo prepares the remastered ISO; it must have a Linux file system with plenty of free space. You can use the default of /tmp to do everything in RAM.">
<default>"'$workingDirectory'"</default>
<variable>workingDirectory</variable>
</entry>

<entry accept="directory" tooltip-text="This is a directory containing files to copy to the file system root of your puplet, /. It is optional.">
<default>"'$stuffDirectory'"</default>
<variable>stuffDirectory</variable>
</entry>

I noticed you have mention that you can use woofy to delete files/programs from a current distro. I also acknowledge you need to know the file and pathname to do this. Is there some way you could make woofy create a list of installed software to make it easier to uninstall. This would be a great feature but would obviously come with risks._________________Puppy Software <-> Distros <-> Puppy Linux Tips

Is there some way you could make woofy create a list of installed software to make it easier to uninstall. This would be a great feature but would obviously come with risks.

I've been busy.. And will be for a bit..

About deleting stuff, at the moment, I just use pfilesearch to build a list of files to delete...
I just search by app name, and use the list of files returned..

For example, I just search for 'abiword' and copy and paste the returned files and folders into a text file.

I repeat this process for all the apps I want removed and then use this list in Woofy..

However...

I am gonna make the delete feature more user friendly in future.. So..
you just give a list of app names and woofy finds and removes all the matching files for you..

This should mean that to delete (most of) the goffice suite, you would simply supply the following list, in a text file:

Code:

abiword
gnumeric
inkscape
inklite
aeksaurus
goffice

I see no reason to have to find and list all packages in the base iso...
.. as long as the stuff you want to delete is in the list, it will be removed.._________________Akita Linux, VLC-GTK, Pup Search, Pup File Search

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'.

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..

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

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..

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.

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