Woof at Github

[Ibidem]

So most of the OS is uniquely Puppy. What then makes a variant Ubuntu or Slacko.?

Has anyone tried Woof on the Slackware or Ubuntu OSs including their X, xorg, gtk+ ?
And then use it to compile rox, jwm, gtkdialog, etc. And boot with Puppy`s boot, guis, etc.?
Another words, a Puppified "other distro". But maybe this is what Precise and Slacko are.
.

Yes; here's a short key:
Upup/Lucid/Precise = Puppified Ubuntu (Lucid = Ubuntu 10.xx based; Precise = Ubuntu 12.xx based)
Dpup = Debian-based Puppy
Spup/Slacko = Slackware-based Puppy
Apup = Arch-based Puppy
And I think there's a couple RPM-derived systems.

It would be interesting to use an OWL or PLD based Puppy...

[sunburnt]

So I think Ibidem`s saying that the "other" Puppies are all the other distro except Puppy scripts & etc.

So the Puppy parts are already separate ( not in woof/woof-code/ )?
And what goes in the support folder.?
.

[mavrothal]

So I think Ibidem`s saying that the "other" Puppies are all the other distro except Puppy scripts & etc.

So the Puppy parts are already separate ( not in woof/woof-code/ )?
And what goes in the support folder.?
.

The rest of the files in /woof (including support folder) are for building the puppies thought few make it to the iso too.

[nilsonmorales]

vicmz wrote

Is it possible to have an initrd that includes a basic set of popular languages to choose from at first, so that users are able to read boot messages in their language (practical for live-CDs) and then install the langpack when they get the desktop?

if you start the translate work for initrd i would like to help you my friend.

[vicmz]

Is it possible to have an initrd that includes a basic set of popular languages to choose from at first, so that users are able to read boot messages in their language (practical for live-CDs) and then install the langpack when they get the desktop?

"Gettexting" the init script is not a good idea as it would require a number of additional libraries in the initrd. However BK's init accepts the "plang" boot parameter (example: de_DE.UTF-8 ) and looks for the corresponding init in /locale/${PLANG%.*}/init (ie /locale/es/init or /locale/es-ES/init )
It also looks for a /PUPPYLANG file that contains the plang argument, in case you want to build a puppy with a different default language. The init script has 60 text messages so is not too much work to do. The only ¨problem¨ is that the language changes must be provided as a series of sed commands in the /locale/${PLANG%.*}/init file
You may want to add as an "enhancement" in the woof-CE/issues and then start working on the translation of the init script!

This is a job for Super L18L!

I wish I was that experienced but currently I'm doing what I actually can, otherwise you guys would have a lot more to fix.

The langpacks already have translations for the initrd through sss domains, but these are applied manually after booting to the desktop. I see Woof will require a different method in order to have new Puppies display a choose-language boot menu. For now it's just an idea, time will tell if this is viable/practical/etc.

[L18L]

... I see Woof will require a different method in order to have new Puppies display a choose-language boot menu. For now it's just an idea, time will tell if this is viable/practical/etc.

Look at other OSes:
-Android (I do know the x86 emulation running on my box): all languages included
-OpenSuSE and others had firstly choice of language
not choose from de es it pt ru.....
but choose from Deutsch Espanol Portugues pу

[mavrothal]

I have already realized this choice in Cutting edge section, see
internationalization of initrd messages at bootup
I did not make its way into woof.

But if it will be done in Woof-CE

Will be done in woof-CE if you can provide a patch for it against the current
woof-CE /woof-code/boot/initrd-tree0/

[L18L]

Will be done in woof-CE if you can provide a patch for it against the current
woof-CE /woof-code/boot/initrd-tree0/

Does it already boot directly into X

[mavrothal]

Will be done in woof-CE if you can provide a patch for it against the current
woof-CE /woof-code/boot/initrd-tree0/

Does it already boot directly into X

If you are asking about woof-CE builds then yes,
Slacko 5.6.3 is the latest woof-CE build and it does boot directly to X.
If you are asking if the initrd.gz has a mini Xserver (Xfbdev, tinyX etc) included, No.

[L18L]

If you are asking if the initrd.gz has a mini Xserver (Xfbdev, tinyX etc) included, No.

Yes, that was what I wanted to ask.
Will initrd.gz ever have a mini Xserver?

[mavrothal]

If you are asking if the initrd.gz has a mini Xserver (Xfbdev, tinyX etc) included, No.

Yes, that was what I wanted to ask.
Will initrd.gz ever have a mini Xserver?

OK. But don't let better become the enemy of good.
Provide a patch for the ASCI supported languages in the initrd till someone (or you) implement X in initrd.

[wanderer]

hi all

does anyone have a list of the minimum number of packages
needed to build a woof that has only x and a browser
hopefully puppy only
no outside distro
or any advice about how to go about doing this
i would like to build a puppy from woof in stages
1. console only
2. x only
3. browser
etc

wanderer

[mavrothal]

does anyone have a list of the minimum number of packages

"Minimum" means different things to different people.
The puppy init will boot a computer to terminal for example but hardly do much more on its own.
What functionality do you want to include?
Take a look here for guidance

[wanderer]

mavrothal

thanks for your help

how does one get the latest snapshot of woof-ce
or for example the woof-ce used to build the latest slacko
i see there is a zip download
but it seems to say this is the original commit
of barry k's woof

wanderer

[Keef]

Could well be this:
https://github.com/puppylinux-woof-CE/woof-CE/releases

[wanderer]

thanks keef

wanderer

[mavrothal]

how does one get the latest snapshot of woof-ce
or for example the woof-ce used to build the latest slacko
i see there is a zip download

Yes, this download is the latest.
In the master branch is the one used to build 5.6.3.
In the testing branch is what is added since then and still under testing.

Could well be this:
https://github.com/puppylinux-woof-CE/woof-CE/releases

This is actually a snapshot of the repo used to built the first sane puppy from the repo. Slacko-5.6.1

[mikeslr]

Hi Devs,

As you are now perhaps the most important group taking Puppy into the future, your consideration of the opinions which may be expressed on this thread, http://murga-linux.com/puppy/viewtopic. ... 875#740875 would be appreciated, and your input welcomed.
I would also welcome any thoughts you may entertain regarding my post which suggested the need for that thread, http://murga-linux.com/puppy/viewtopic. ... 863#740863.

mikesLr

[Ted Dog]

I signed up and got a 22M download... Is that it? how do I setup the T2 compilation environment for wary racy builds? just feels like I missing something. I'm stuck in town due to a fall and ER visit that left me on powerful pain meds. zo Im ready to debug code.

[Keef]

Run 'merge2out' - you make your intial choices there.
Then go up a directory and you will find a 'woof-out_x86_x86_t2_racy6' directory.
Enter that, and follow your nose...

Of course, I have been know to be completely wrong about these things.