Puppy 4.2 & WOOF! Comparison?

[edoc]

Can someone post a compare & contrast of Puppy 4.2 (and future releases) with the goals of the WOOF! project, please?

Other than WOOF! having the capacity to import Debian or Ubuntu apps I am unclear as to what separates the "Community" version from the WOOF! version and imagine others may be as well.

[WhoDo]

Can someone post a compare & contrast of Puppy 4.2 (and future releases) with the goals of the WOOF! project, please?

Other than WOOF! having the capacity to import Debian or Ubuntu apps I am unclear as to what separates the "Community" version from the WOOF! version and imagine others may be as well.

Ok, edoc, first some basics:

1. Woof is NOT a Puppy version but a Puppy build system. The appropriate comparison there is Woof vs Unleashed. Unleashed builds plain Puppy's really easily but takes a lot of initial maneuvering to build a version compatible with something else such as Slackware, as in the Puppy 3.x series. Woof makes the process of building in compatibility a whole LOT easier.

2. Puppy 4.2 was built from Unleashed. There are other puplets out there being tested and played with that were built from the alpha release of Woof, such as dpup (Debian compatible) and upup (Ubuntu compatible)! Like any Alpha, it needs work but IMHO the Woof build system will be terrific when Barry is finished with it.

3. Puppy 4.3 will likely be built from 4.2 Unleashed and packages managed by Git, a software development repository being tested by the devs and led by Pizzasgood. What functionality it contains will be up to the community and the coordinator for that release.

4. Puppy 5.x will likely be built from elements of 4.2 using Woof and packages built or stored and managed by both Git and the repositories of the compatible distribution. What it contains will be up to Barry (at first, I think), then the community and the coordinator for subsequent releases, or even individual puplet creators themselves.

That's the way I understand things, edoc. Barry has said many times, in his blog and elsewhere, Woof isn't Puppy ... it BUILDS Puppy. I hope that helps.

Cheers

[edoc]

Perfect!

I read bits and pieces of Barry's Blog but missed that critical tidbit.

Have been dealing with outside projects and some radio-related repairs here so have not gotten beyond my early tests with 4.2-Final, though I like most of what I have seen so far!

Sure appreciate all that you guys do - wish I had the knowledge to be of more help - my talent seems to lie in breaking things!

[WhoDo]

Sure appreciate all that you guys do - wish I had the knowledge to be of more help - my talent seems to lie in breaking things!

Hey, don't knock that talent edoc. A good "wrecker" is worth his or her weight in jam doughnuts to any software development test program!

[edoc]

Never had found a way to get paid for my "unique talent".

Sure would make for a fun work-from-home job!

I used to know a guy with a company whose theme was "You make it,we break it."

They did the stress tests for certification - highly sophisticated equipment for freezing, heating, dropping, banging, shaking, etc. and measuring what they did and what were the results.

Some guys have all the fun!

[Jim1911]

@whodo

1. Woof is NOT a Puppy version but a Puppy build system. The appropriate comparison there is Woof vs Unleashed. Unleashed builds plain Puppy's really easily but takes a lot of initial maneuvering to build a version compatible with something else such as Slackware, as in the Puppy 3.x series. Woof makes the process of building in compatibility a whole LOT easier.

Your description is right on the mark, Barry has already used Woof to build version 4.1.3 per his blog http://puppylinux.com/blog/?page=1

Jim

[edoc]

Wow & wow & wow again!

Or should that be bowwow, bowwow, bowwow ... like our Dalmation-lab who was just carrying on outside my window?

That is amazing timing and exciting news!

I must have something I can try that on here ...

[Lobster]

Puppy 4.3 will likely be built from 4.2 Unleashed and packages managed by Git, a software development repository being tested by the devs and led by Pizzasgood. What functionality it contains will be up to the community and the coordinator for that release.

The new ppup 'proof of concept' looks interesting.
Will Ppup be using Git?


Warren I am pretty sure you will be doing 4.2.1 (patch release)
Are you still planning to do your own puplet / CE version of 4.2?
Are you interested in coordinating 4.3 and 5.xx?

Anyway some of your points added here
http://www.puppylinux.org/wiki/developm ... ppy-kennel

[WhoDo]

The new ppup 'proof of concept' looks interesting.
Will Ppup be using Git?

If Pizzasgood, Barry and I can integrate Woof into the Git server, all of the Puppy Purebreds (ppup) and Crossbreds (spup, apup, dpup, upup) will be using Git for core package development.

Warren I am pretty sure you will be doing 4.2.1 (patch release) Are you still planning to do your own puplet / CE version of 4.2? Are you interested in coordinating 4.3 and 5.xx?

If there is to be a 4.2.1 and/or 4.3, it makes sense for me to continue coordinating that effort, to ensure a smooth transition from Unleashed to Git. I think we may see Barry take the reigns for Puppy 5.x if that is the first Woof-built hybrid release, but if he doesn't want to do that, I'm still willing to continue ... unless someone else better qualified would like to take over.

I'm just not "precious" about the project leadership, Ed. I was truly shocked when the announcement of 4.2 at Distrowatch carried my name! I wasn't expecting that and would have been perfectly happy if they had said the announcement came from the "Puppy Community" or continued to credit Barry with the official announcement. Of course I was proud to see it, but a little embarrassed too. It didn't feel right for my name to be occupying a position normally reserved for guru's like Barry Kauler, Warren Woodford (MEPIS) and Patrick Volkerding (Slackware). It still doesn't.

Now that 4.2 is out there, I can relax and reflect on how much fun it was to meet all the challenges and solve the problems of a complex development process. At the time, especially toward the end, all I really wanted was some respite from the pressure to deliver a decent product for Barry and the community. I remember a similar feeling when 2.15CE was finally rolled out about 2 years ago. I said "Never again" back then and look where I am right now!

The straight answer is I'll do it if Barry, the developers and the community want it that way. If Barry wants the reigns back for 5.x, I'll happily hand them over. If someone better qualified steps up, the same deal. Other than that I guess you guys are stuck with me for a little while longer.

[Lobster]

. . . ensure a smooth transition from Unleashed to Git

I believe you you are in tune with the sentiments of the Puppy Commun ity. I too would like Barry to coordinate 5.xx
Any chance Barry?
I think your efforts Warren on 4.2 with great support from Team Puppy, proves you are able to move us into a more community orientated distribution with strong but patient and able leadership. A quality that Barry too exhibits.

Puppy - the legend continues . . .

[WN2A]

Nice Job Warren! An incredible feat pulling off a really fine Community Edition! No idea why we keep coming back to do these type of things. We just do. I'll just keep writing with some (relatively simple) programs and crank out the next version.