Woof at Github

Message

01micko · #81 Post by **01micko** » Mon 18 Nov 2013, 21:09

As far as repo's goes, I have asked ibiblio for an account. Haven't heard back yet but I guess they get a heap of mail.

One possible solution to P-apps is to state the version number in DISTRO_PKGS_SPECS. This is quite easy as I do it all the time with different kernel_headers packages. (look at the one provided in ~/.packages in any slacko for an example).

When my account does get approved it might be time to reduce dependency on Barry's Quirky repo, then we can move pet_packages-common, pet_packages-noarch (etc) to the Puppy repo. Of course we don't want to touch BK's stuff in the Quirky repo.

Of course pet_packages-{precise,dpup(?squeeze,wheezy?),mageia} etc would need to be set up too.

It's early days, we'll get to these things in due course.

ally · #82 Post by **ally** » Mon 18 Nov 2013, 21:19

I have just starting uploading a mirror of the common packages from ibiblio here:

http://archive.org/details/Puppy_Linux_ ... Repository

I will add no-arch in response to micko's comments

unfortunately I could not have additional accounts added for uploading (?) but anyone can upload and then ask to have the files moved to the appropriate page

in the mean time files can emailed to me and I can put them up

anything else you needed let me know if I can help....

ally

edit http://archive.org/details/Puppy_Linux_ ... Repository

mavrothal · #83 Post by **mavrothal** » Tue 19 Nov 2013, 05:00

01micko wrote: It's early days, we'll get to these things in due course.

Very true.
But having control over your repo is vital for the building process and its rationale and the maintenance/update of the packages/pets.

The second reason is that building from other distros or even LFS can really generate problems and bloat (I'm playing with compiling these days

), so we will need puppy-specific packages by capable compilers (where are they these days?

)

go2null · #84 Post by **go2null** » Wed 20 Nov 2013, 15:57

01micko wrote:Probably a good idea to set up and configure git.

In the short term:
Code: Select all
git config --global http.sslVerify false
That should work.

Other wise, go to the site and grab the tarball.

Didn't really want to disable SSL Verification, so did a google and found this:
http://derekmolloy.ie/fixing-git-and-cu ... bone-blac/

After installing ca-certificates_20130119 with PPM, git still complained.

This was fixed by going to http://packages.ubuntu.com/raring/all/c ... s/filelist and found the reference to /usr/sbin/update-ca-certificates.

After running this, was able to clone successfully.

*NOTE*: Running git from the console didn't work off the bat. A quick reinstall of git_1.8.1.2-1 with PPM fixed that.

[EDIT] Fixed missing leading "/" in "/usr..."

pemasu · #85 Post by **pemasu** » Wed 20 Nov 2013, 16:51

This fix is valid for git ssl error:
http://murga-linux.com/puppy/viewtopic. ... 154#713154

oldyeller · #86 Post by **oldyeller** » Fri 22 Nov 2013, 09:21

Hello Everyone,

I have gotten OVPrecise 5.8 and OVPrecise-retro 5.8 Finalized

You all can find it here http://www.murga-linux.com/puppy/viewto ... 641#738641.

Have fun!

vicmz · #87 Post by **vicmz** » Fri 22 Nov 2013, 18:08

mavrothal wrote:So we (me, 01micko and pemasu - we welcome new members in the team) just opened a project on Github to host woof as derived from Barry's repo on November 11, 2013.

Then all the effort for multilingual support in Puppy Linux will remain and can be further enhanced, and all Puppies made from Woof-CE will be compatible with the existing language packs, meaning that newer Puppies will not go back to English-only but will be international from the beginning. Great!

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?

mavrothal · #88 Post by **mavrothal** » Fri 22 Nov 2013, 19:06

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?

"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!

zigbert · #89 Post by **zigbert** » Fri 22 Nov 2013, 21:08

I have done some initial testing of gui enhancements in woof.
My guidelines

Only touch gtkdialog code
Take advantages of the recent gtkdialog features
Allow scaling of window
Clean up gui
Make gui code more human readable
Change gtkdialog3/4 to gtkdialog

Is this something for 'zigbert winter of code'?

Iguleder · #90 Post by **Iguleder** » Fri 22 Nov 2013, 21:11

Good to have one of our gtkdialog experts on the woof-CE board

mavrothal · #91 Post by **mavrothal** » Fri 22 Nov 2013, 21:38

zigbert wrote:I have done some initial testing of gui enhancements in woof.
My guidelines
Only touch gtkdialog code

Take advantages of the recent gtkdialog features

Allow scaling of window

Clean up gui

Make gui code more human readable

Change gtkdialog3/4 to gtkdialog

Make it touch friendly ?

BarryK · #92 Post by **BarryK** » Sat 23 Nov 2013, 02:20

This is a great initiative!

I kept very quiet for sometime, wondering if something like this would spontaneously emerge, and it has!

Created and supported by long-time rock-solid guys too!

Yes, there are many who will now get a more direct input to the evolution of Woof and Puppy, than before, when everything channeled through me.

I have announced woof-CE in my new blog:

http://bkhome.org/news/?viewDetailed=00002

I wish you guys great success.

Let me know when a pup distro gets to release status and I'll announce it on my blog and at Distrowatch.

puppyluvr · #93 Post by **puppyluvr** » Sat 23 Nov 2013, 02:47

Hello,
Great project to provide Woof with a future.
Great to see the Puppy Master on board!

shinobar · #94 Post by **shinobar** » Sat 23 Nov 2013, 03:37

Great!

01micko · #95 Post by **01micko** » Sat 23 Nov 2013, 05:19

Slacko -testing, woof-CE (testing branch).

Reports here please.

sunburnt · #96 Post by **sunburnt** » Sat 23 Nov 2013, 08:11

I`ve had a long time Q that`s never been answered. And these are the folks that would know.
What part of a Woof build is uniquely Puppy.? I`d think: guis, scripts, Rox, JWM, GtkDialog.
But are all the os core files the parent distro`s.? /bin, /lib, /sbin, usr/......., X, xorg, gtk+.
I don`t want to pollute this thread, so if someone wants to pm me with an answer, great.!

mavrothal · #97 Post by **mavrothal** » Sat 23 Nov 2013, 08:36

sunburnt wrote: What part of a Woof build is uniquely Puppy.?

Assuming you are referring to the produced ISO, whatever is in woof/woof-code/ but the scripts and the support folder, and all the pets that are used in a build (check DISTRO_PKGS_SPECS)

amigo · #98 Post by **amigo** » Sat 23 Nov 2013, 15:32

What part of a Woof build is uniquely Puppy.? Exactly the right question -because all that needs to be separated out, conceptually. Since that's where most development takes place and where there are most likely to be bugs, it should be treated as separate entities so it gets the needed attention.

mavrothal · #99 Post by **mavrothal** » Sat 23 Nov 2013, 16:45

amigo wrote:What part of a Woof build is uniquely Puppy.? Exactly the right question -because all that needs to be separated out, conceptually. Since that's where most development takes place and where there are most likely to be bugs, it should be treated as separate entities so it gets the needed attention.

Technically as I said is what ever is in the woof-code folder. Conceptually, though I'm certainly not the best qualified to tell you, I would think the boot sequence, ie init script and rc.d scripts, the (ever argued upon) puppy package manager, the plethora of (mostly) gtkdilog-based customization apps (wizards) and to a lesser extend the ROX-JWM desktop, the (ever controversial) menu system and the hardware detection scripts (though lately udev and Xorg are mostly used for that).
The underlining theme in all these I believe is try to do some things in a simpler yet effective way without the bloat and the cascading dependencies of mainstream GNU/Linux.
Regarding separating them, I'm not sure I would agree. This exact separation I think is responsible to a great extend for the escalating size and dependencies of linux builds.

sunburnt · #100 Post by **sunburnt** » Sun 24 Nov 2013, 03:43

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

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Woof at Github

How to fix SSL CA Certificate issue

Re: Woof at Github

Re: Woof at Github

Re:Woof-CE