Official SFS for desktops

[R-S-H]

?!? Stay on topic please !

that ist that lvds!

you find your suggestion interesting but it is silly dilly:

all above puppy have the classic presentation of a real Puppy: the same as on my little snapshot:

you want to wring the poor Puppy stuff as long as it become not be a Puppy any more because you add code and code for absolutely not needed new function not offered by the biggest distributions...

Puppy has long been a chubby and sick puppy under such impulsions requiring transform it heavily.

How can you say this when so many people are working each month to improve the desktop experience ! Everyone is working hard, from newcomers to veterans, Toopy, Jejy69 and many others to build new desktops, some works better than others but everyone is trying hard ! We need some modularity in the base puppy so we integrate easily the developpers works and move from one desktop another without recompiling / rebuilding / remastering new pupplets ! This is just pure reason. We need some way to give mainstream users easier access to the desktops the devs are working so hard on.

If you don't agree with the idea, stay off the topic and don't disgust others.

Hi.

Just want to make clear: I don't want to hurt anyone, it's just the way I talk to my people when it comes to the bloated desktops. Really, I do appreciate the work done on MacPup or LXPup f.e. and they're working very well and looking also very fine - it's just me: I don't need it.

But because of the nice look of MacPup and LXPup I did add some LazY Puppy comfort to these Operating Systems and build new remasters. Some of you might know, that I'm giving away USB flash drives with LazY Puppy installed (to friends, on birthdays etc.pp.). Because of my people also do like the bloated desktops, the MacPup and also the LXPup remasters are now used for these give away USB flash drives!

@R-S-H
Here is unofficial Unity repository for Arch
http://pkgbuild.com/~bgyorgy/ayatana/os/i686/

off course with unity-lens-shopping-6.8.0-2-i686.pkg.tar.xz

Thanks for the Link. I was just kidding. I really don't need this!

RSH

[backi]

HI !

Here is a new E17 Enlightenment Desktop Pet from pemasu working fine for me on Precise puppy 5.5.9 .
Did not made an Sfs file from it so dont know if and how it works as Sfs file .

http://murga-linux.com/puppy/viewtopic.php?t=71058

[R-S-H]

Hi.

Window Manager e17 running in my Osiris Studio (LazY Puppy Derivative). Did need to make a few modifications for the use of LazY Puppy Shutdown-GUI. Seems to work well.

I did install into the OS running a save file. I will try to add this to a remaster because I think this can not be used from SFS (maybe it will work if the SFS is loaded at boot up) - install message is saying: needs to reboot before puppy will use the libraries in /opt.

RSH

[backi]

Hi RHS !

Like your interest for E17 .
Its my number one .

Want to ask you is there a chance for downloading Your OSIRIS STUDIO iso ,
or is it just a privat experiment ?

Cheers ..keep on rocking ..!

[gcmartin]

I dont know if this is useful at all, but if it is, run with it.

KNOPPIX, for years, has offered the selection on the desktop as a boot-time option. Would this be something which could/would ever be employed in the Puppy world?

I truly understand that the distro build would have to offer it AND I truly understand the storage impact on the ISO. But, ISO size is merely the things needed to boot the system...NOT what is actually running in the system. So, as such, there will be those where a larger ISO would not be recieved warmly merely because of the download impact..

But for those where this would NOT be a hardship, an ISO offering these options (or someone offering a USB/DVD) this might actually work.

Also, Knoppix offers an additional option at boot-time ... boot a 32bit version or boot the 64bit version. This too, could provide some very interesting possibility in Puppyland, too.

Can this kind of packaging technique(s) work in Puppyland?

[lvds]

I dont know if this is useful at all, but if it is, run with it.

KNOPPIX, for years, has offered the selection on the desktop as a boot-time option. Would this be something which could/would ever be employed in the Puppy world?

I truly understand that the distro build would have to offer it AND I truly understand the storage impact on the ISO. But, ISO size is merely the things needed to boot the system...NOT what is actually running in the system. So, as such, there will be those where a larger ISO would not be recieved warmly merely because of the download impact..

But for those where this would NOT be a hardship, an ISO offering these options (or someone offering a USB/DVD) this might actually work.

Also, Knoppix offers an additional option at boot-time ... boot a 32bit version or boot the 64bit version. This too, could provide some very interesting possibility in Puppyland, too.

Can this kind of packaging technique(s) work in Puppyland?

If each desktop are all in .SFS independant files, that would not have any impact on the size of the iso

[simargl]

.

[lvds]

If each desktop are all in .SFS independant files, that would not have any impact on the size of the iso

That was already used in Archpup and will be in its continuation project alphaOS 7.

in DISTRO_SPECS I add this

....
DISTRO_ADRVSFS='extra_70.sfs'
DISTRO_BDRVSFS='desktop_*.sfs'
...

(off course init script needs adjucting for this to work)

those two sfs are optional; with just DISTRO_PUPPYSFS system boots to console,
with DISTRO_PUPPYSFS and DISTRO_ADRVSFS it startx Xorg with openbox window manager.

Default iso does not have DISTRO_BDRVSFS, but if it's present it will be loaded so that gives option for additional desktop.

You could make desktop_xfce.sfs desktop_gnome.sfs desktop_kde.sfs, and just switch between them, DISTRO_ADRVSFS has applications that can be used with any desktop.

That's exactly the idea !

Barry, please, tell us what you think about it ?

A lot of people could benefit from this and it would cost nothing to the weight of the distro.

Also, simargl, please can you explain how you set up woof build so to install a desktop (example with xfce or lxde or kde whatever) into BDRVSFS ? Is it done at woof build ? or do you build a SFS afterwhile ? and how do you create this SFS ?

Many thanks

[simargl]

.

[Pelo]

Where is the problem : we have already desktops available in pet repository or SFS. That's work fine; Go on that way.
LXDE, XFCE, KDe, E17 .... You choose as you like. But keep all old versions available please (KDE 3XXX).

I sometime dress my distros with XFCE, but JWM must be kept as the default choice, in my opinion.

[lvds]

Where is the problem : we have already desktops available in pet repository or SFS. That's work fine;

The problem is it does not works fine

That's why we need a hook into the official puppy release to link to whatever desktop we need instead of having a desktop built-in in puppy. There is no need to change the jwm/rox desktop that Barry loves. Keep it but into an SFS. Then we can release alternatives desktop official SFS files depending on the puppy release. Because some desktop SFS works into some release while they stop working elsewhere, and that is not documented: the end-user have to test and crash -> not good.

This would also allow builders to build much better desktops solutions.

[akash_rawal]

That's why we need a hook into the official puppy release to link to whatever desktop we need instead of having a desktop built-in in puppy. There is no need to change the jwm/rox desktop that Barry loves. Keep it but into an SFS. Then we can release alternatives desktop official SFS files depending on the puppy release. Because some desktop SFS works into some release while they stop working elsewhere, and that is not documented: the end-user have to test and crash -> not good.

I think I misunderstood you. You meant changing SFS files to change the current desktop environment?

That will only be an extra hassle for both the user and the developer.

As I already mentioned, lots of scripts need to be adjusted to make things work with a new desktop environment.

Bundling these changes in the desktop environment pet or sfs, as it is done now, breaks things whenever scripts change in incompatible way or the user makes changes to those scripts.

Ideally no pet or sfs package should clobber any file in the system.

Hence it is more beneficial to make the things modular so that all the adjustments can be made without changing any file. This will ensure that desktop environment pets and sfs will continue to work wherever there is binary compatibility. This will also reduce a lot of effort in creating those pets and sfs. (e.g. count the total no. of lines in the LXDE example at http://www.murga-linux.com/puppy/viewto ... 561#703561)

[sunburnt]

I had trouble with the original thought also.
It seemed to be a single "base SFS" file for all Puppies, which is impossible.

However I`ve suggested a Puppy stripped of all apps. except needed utilities.
And use only no-install apps.: SFS, RoxApp, or AppDir.
NO .pet or .tar.gz packages, as they fill up the Save file, no-install apps. don`t.

So apps. ( desktops, etc...) are easily added and removed.
.