woof-CE needs you

[Iguleder]

Hello everyone,

woof-CE needs you!

Great things are happening in the "testing" branch of woof-CE:
- Support for building tahrpup64
- Support for packages of more distros and more distro versions
- Speed improvements, new looks and new features in PPM
- Support for new kernels
- UI improvements
- Bug fixes
- New translations
- ... and more

Many Puppy developers produce their puplets by remastering an existing Puppy built using woof-CE, so they don't receive all those new features. For example, if someone builds a puplet from tahrpup 6.0.2, it won't benefit from the features added to woof-CE after tahrpup 6.0.2 was released. Also, this means the additions to woof-CE are less battle-tested.

It's sad that puplets remain oudated, while all these features are already available and waiting for someone to take advantage of them. And they don't cost money, so why not?



I want YOU to use woof-CE. It's always good to have more working hands and thinking minds in a community project like this.

Therefore, I encourage you:
- If your puplet includes non-trivial changes (i.e it's more than just a different wallpaper), build it using woof-CE and not by remastering. This way, you gain new features and have much more control: you can change everything in your puplet. To use woof-CE:

Code: Select all

git clone https://github.com/puppylinux-woof-CE/woof-CE.git -b testing
cd woof-CE
./merge2out
cd ../woof-out*

./0setup
./1download
./2createpackages
./3builddistro-Z

See? It's simple. If you're new to woof-CE, try to build tahrpup (x86, x86, ubuntu, trusty) first. Then, edit files under woof-distro/x86/ubuntu/trusty until you get the knack of it.
- Contribute all bug fixes in your puplets back to woof-CE, so other puplet developers don't have to fix them again
- To contribute all changes you do to woof-CE, using a git pull request (see GitHub's documentation). This way, the entire Puppy ecosystem benefits from them.
- Maintain your puplet's configuration files under woof-distro directly in woof-CE. This way, you have all the features of modern version control (full history, the ability to track changes, branches, the ability to revert changes and see when they happened ...) while making it easier for others to join the development.
- If you're serious about Puppy development, join the woof-CE organization in GitHub.

If you have any questions, feel free to PM or email me.

Cheers,
Dima

[mavrothal]

woof-CE needs you!

+1
As a matter of fact there are more than 170,000 lines of code changed since woof-CE started 2 years ago, and in reality only 2 "official" and 3 alpha/beta puppies where build from it.

- Contribute all bug fixes in your puplets back to woof-CE, so other puplet developers don't have to fix them again

+1000
Actually the feedback from the last official puppy was surprisingly limited and almost none from its many remasters.

- Support for building tahrpup64

Almost... 666philb's tahrpup64 configuration files are not pushed into woof yet

[666philb]

- Support for building tahrpup64

Almost... 666philb's tahrpup64 configuration files are not pushed into woof yet

pull request issued

[mavrothal]

pull request issued

Where? just checked?

[666philb]

had a few issues and temporarily removed it ... but it's been pulled now ...thanks

[01micko]

I took care of it.

[musher0]

push, pull. Speaking jargon, are we?

[01micko]

push, pull. Speaking jargon, are we?

Why yes we are !!!

Extreme shorthand answer -

To grab changes from remote git repository (github or other - you can host your own plus there are other public git servers) :

Code: Select all

git pull

To make changes to remote git repository:

Code: Select all

git push

Further reading: http://rogerdudler.github.io/git-guide/. This is certainly not the definitive git guide!

[bigpup]

Is there something that explains how to use Woof-CE?
The people that have been using Woof-CE seem to understand, but what about someone new??

There is the readme-first.

However, someone new to all of this is going to need a little hand holding type of readme.

Could they understand this?

From Woof-CE readme-first.

To create a working directory, named 'woof-out_*', that you will then use just like you did before with Woof1, you first have to run the 'merge2out' script. This merges the three directories into a directory named 'woof-out-*'.
You then 'cd' into woof-out_* and run the usual Puppy build scripts.

[musher0]

I agree with bigpup. The woof-CE process requires a capacity for abstraction
that not everybody has. Remastering is more concrete: remove that, add
this, juggle some files from here to there; it's simple by comparison.

[bigpup]

Let me show my lack of knowledge

From:
http://bkhome.org/woof/

Does Woof-CE have one of these?

[Ted Dog]

Since yesterday

127 Registered, 13 Hidden

Should I point out the elephant not in the room? Also what could we do if say a person wants to overhaul the underpinnings of puppylinux? Major fork? My dream is a rolling update style, had it mapped out for years and was hoping BK was going that direction with April <would be VERY similar if not identical > but without support for optical save backs or ISOs setups April never made it. But April gives you the idea puppylinux in look and action but different way of getting it started and ended.
Second, why not a T2 version release? Never been a fan of inheriting other distros bloat and problems even when we can bend its compiled code into puppylinux mode ( which is SO cool ) but since the end of 4 series puppylinux got LESS stable. I am a fan of Slacko64 (stable) is that supported, has the main guy who made it left?
Its getting to be cold weather and heat is heat regardless of source so I DO try my hand at large builds with a server farm of old computers.

[Ted Dog]

I guess if BK would add his April fork back to woof-CE then I would extend it to make my idea work ( again it so alike would be sad to have to redo it, slight change with roll back delta method, a ISO build and saveback ) . That would be easiest for me, not sure if BK would be OK with it.
After Rolling Puppy is rolling then figure out how to add kernel changes to the mix ( most likely need to start a new disc for each kernel upgrade )
Also not just looking at optical discs but also other media, see how fatdog64 does multisession for a real live example. Replace the construction of saveback session to the April method ( but reverse the delta construction for rolled forward verse rollback ) and you got it. simple ah?

[Iguleder]

Is there something that explains how to use Woof-CE?

Yes, the first post. I gave you the exact command lines to run, what else do you need?

[zigbert]

Great to see things rolling...
I will hopefully be back later this fall.

[Ted Dog]

no rush for answers, my server farm is in deep storage and I have no place to set it up for a few weeks to months need to move but no place ready, RV at ranch too small. Personal issues <lost tire = accident while driving not resolved fully> and many hospital trips and surgeries to worry over this month.

[slavvo67]

First post seems a bit too simplified:

sh-4.3# git clone https://github.com/puppylinux-woof-CE/woof-CE.git -b testing
Cloning into 'woof-CE'...
fatal: unable to access 'https://github.com/puppylinux-woof-CE/woof-CE.git/': Problem with the SSL CA cert (path? access rights?)

[Iguleder]

No, it's not! Something is wrong with your system's /etc/ssl.

[slavvo67]

I'm running Barry's QU 6.2.1 Any suggestions? I just logged in and downloaded the .zip file using the browser, instead. It didn't take long. I'm up to the ./0setup stage and it seems to be working fine, this way.


Do you need to login to Github via terminal before the git instruction?

And you're right, the etc/ssl is empty in my QU.

[musher0]

@Iguleder:

Thanks for the invitation, and your enthusiasm is communicative!

However, looking at your first line of code:
Any reason why you are directing users to use the "testing" branch
instead of the "master" branch?

I have no experience of woof-CE, but in Debian, the "testing" branch is
recommended for very advanced users only, because users with average
knowledge of Linux may be stumped by the bugs that remain in the
"testing" branch.

Wouldn't the "master" branch of woof-CE produce a more stable Puppy?
Referring to my previous post, wouldn't the "master" branch require
less power of abstraction on the part of users, I mean: be easier to
understand and conceptualize?

I'm not "questioning" anything here, I'm just putting a toe in the river
before my first swimming lesson, so to speak.

BFN.

musher0