woof-CE needs you

[musher0]

There you go, belham2:

"C'en est fait, je n'en puis plus, je me meurs, je suis mort,
je suis enterré."

Transl. : "The deed is done, I can't stand it anymore, I am dying, I am dead,
I am buried."

(Molière, excerpt from L'Avare [The Miser],
monologue "Au voleur !" ["I've been robbed!"])

[Sailor Enceladus]

I tried a new Slacko 32-bit build in woof-CE today, and was very happy to see that clicking on rar files now works and extracts them AND right-clicking on things lets me open them with gnome-mplayer! Sweeeeet. Best version ever. 01micko rocks!

[musher0]

Yeah, seemed the dpup-stretch development was really going gangbusters, and suddenly *poof*... crickets. A real shame! A great deal of potential there, towards a next (hopefully?) official Pup release.

I soo very wish I had the chops/time/energy, as I'd be geeked to pick it up and run with it...

Puppy needs it, Puppy deserves it!

Bob

Hi Moat and all.

Some prefer to work in the shadows to avoid controversy.
http://murga-linux.com/puppy/viewtopic.php?t=109904

It's labeled as "French" but it's actually a bilingual French-English version.
If the LANG variable for your system is en_??, everything will show up in
English.

There are three iso's available of it, with each its own kernel.

I thank Billtoo who allowed me to use some of his DPup builds and augras
for setting up the pydio repository.

One reason for working in the shadows is that I wish to offer alternative
WM's, aewm for ex., in Puppy.

Another reason is that the Woof-CE, whatever the "Puppy breed", is
mostly offering the "same old, same old" choice of apps, which IMO are
not always the best suited for an international environment.

Improving the Woof-CE only improves the Woof-CE, meaning: the making
of one and only one type of Puppy, whereas Puppy is capable of and
should be encouraging all sorts of explorations.

Not just making a better straight-jacket, which IMO is what's happening
with the Woof-CE process. Or making a better robot, since the Woof-CE
can be viewed as a robot, come to think of it. A helpful robot, no doubt,
but still a robot. And a human can only go so far with a robot.

Nobody at the Woof-CE level seems to have paid any attention to
josejp2424's pupjibaro's Jessie abandoning the PPM, and to reports that
the PPM is not working as expected when the Puppy is running as a
French system.

Enough said. Remastering still has its virtues -- and pkgs.org!

BFN.

[Billtoo]

I tried a new Slacko 32-bit build in woof-CE today,

I did a 32bit 6.9.9.5 build on Sunday, added a bunch of stuff from PPM + a few pets and slackbuilds, then did a remaster that weighs in at 796 mb

This one is working pretty well too.

[Lassar]

Someone's been busy fixing woof-ce.

Now in xenialpup, woof-ce goes all the way to the end & creates a iso.

On the first burned cd, it boots up good.

On a remaster of this cd, I get error "failed to load ldlinux.c32"

Looks like a problem with remasterpup2.

Is there any other remaster scripts, that will remaster the cd?

[Sailor Enceladus]

Is there any other remaster scripts, that will remaster the cd?

musher0 mentioned a program called Remasterx here:
http://www.murga-linux.com/puppy/viewto ... 034#948034

shinobar says: "Intend to replace the remasterpup2, Puppy Live CD Remastering tool."

[Billtoo]

There's been a lot of activity in woof-CE since my last build so I did a
new one this afternoon.

# inxi -b
System: Host: puppypc364 Kernel: 4.1.39-pae i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.5
Machine: Device: laptop System: Apple product: Macmini6 1 v: 1.0 serial:
Mobo: Apple model: Mac-031AEE4D24BFF0B1 v: Macmini6 1 serial:
BIOS: Apple v: MM61.88Z.0106.B03.1211161202 date: 11/16/2012
CPU: Dual core Intel Core i5-3210M (-HT-MCP-) speed/max: 1200/2501 MHz
Graphics: Card: Intel 3rd Gen Core processor Graphics Controller
Display Server: X.org 1.18.3 driver: intel tty size: 140x41 Advanced Data: N/A for root
Network: Card-1: Broadcom Limited NetXtreme BCM57766 Gigabit Ethernet PCIe driver: tg3
Card-2: Broadcom Limited BCM4331 802.11a/b/g/n driver: bcma-pci-bridge
Drives: HDD Total Size: 1500.3GB (4.1% used)
Info: Processes: 132 Uptime: 1:46 Memory: 195.9/16112.0MB Client: Shell (bash) inxi: 2.3.8
#

I bought an adapter for my Macmini that is mini display port to vga so
with the help of lxrandr it supports 2 monitors, (a 32" tv and a 23"
lcd).

It's working well so far.

EDIT: I made a pet of Gtkhash if anyone wants it.

[Sailor Enceladus]

I built another Slackware 14.2 32-bit and 64-bit iso today with woof-CE too, the fixes were too good to pass up

[Lassar]

I just spent quite a bit of time, working on DISTRO_PKGS_SPECS-ubuntu-xenial.

I just read in _00build.conf file, that you can do a through dependency check.

Maybe I didn't have to do all that work!

My question is how to do get woof-ce to use kodi 17.3 pet?

This kodi pet is on my harddrive. Does it have to be on a website?

Found PKGS_HOMEPAGES in the woof-out_x86_x86_ubuntu_xenial folder.

But almost no info on this file.

Can I add a local file url to this file?

How do I get woof-ce to add the kodi pet to the packages?

[peebee]

How do I get woof-ce to add the kodi pet to the packages?

Hi
You need to:
1. put the kodi.pet into /local-repositories/x86/packages-pet
2. add a line for the petspec somewhere - you can either add it to an existing repo list such as Packages-puppy-slacko14.2-official or you can have your own list but then you will also need to edit DISTRO_PET_REPOS to make it aware of the new list. (in both cases if you don't have a web repo then you will get some errors in ./0setup)
3. add kodi to your DISTRO_PKGS_SPECS-***

If you want to see examples (from LxPupSc) - http://smokey01.com/peebee/slackocurrent/

Cheers
peebee

p.s. locations will change if you are 64-bit or not slackware based.....

[Sailor Enceladus]

Re: Need info on how to add custom pet to woof-ce

The way I usually do it is just rename the pet to tar, then extract it to rootfs-packages (using the 2nd field in pet.specs as the folder name), then select it in ./3builddistro-Z when asked. It's quick but less clean than the official way I guess. Sometimes I have to actually edit 3builddistro-Z and add it here if the name is too similar to another package though.

[Lassar]

I put kodi-17.3.pet into /local-repositories/x86/packages-pet, and
edit the DISTRO_PKGS_SPECS-ubuntu-xenial.

yes|kodi|kodi-17.3|exe,dev,doc,nls|

Run ./2createpackages, and build package kodi.

I am getting error:

Code: Select all

ERROR: 'kodi-17.3' package does not exist.
You will need to find a matching package and place in packages-pet,
or packages-deb-xenial as appropriate.
Do it, then rerun this script and choose to build kodi-17.3.

What am I doing wrong?

[Sailor Enceladus]

What am I doing wrong?

Nothing wrong per se, but you missed step #2 (the most annoying step probably ) in peebee's post.

[Lassar]

Not really understanding step 2.

After reading DISTRO_PET_REPOS, it sounds like I have to upload kodi-17.3 to a repo.

I thought there was a way to use a local pet, and not have to use a remote repo,

[peebee]

yes|kodi|kodi-17.3|exe,dev,doc,nls|
What am I doing wrong?

The line for a single .pet is:
yes|kodi||exe

but you also need to extract the petspec line out of the .pet (easiest way just rename a copy of the kodi.pet to kodi.tar.gz and use xarchive) and put that line into an existing repo list

[belham2]

Hello all,

Have a a question about all these woof-CE builds I've been doing the past 2-3 months.

Do I need to re-download everything to get the latest & up-to-date changes in whatever build I am doing?

I've always just deleted the "Local Repositories" and the "Woof-Out_x86_64 (or just x86)_######" folders, and kept the Woof-CE folder.

Should I be also re-downloading the Woof-CE folder too if I want the latest of whatever I build???


Thanks for any replies.

[Sailor Enceladus]

@belham2: I think, unless a pet has been updated without changing the name (which doesn't happen very often), keeping your old local-repositories directory for a newer build is ok. During ./1download, whatever is already in local-repositories directory will be skipped and whatever isn't will be downloaded. I think grabbing the latest woof-CE directory is always what you want though, unless you have something against the people who make changes to woof-CE or think a recent commit will bork something.

[Lassar]

...extract the petspec line out of the .pet...and put that line into an existing repo list

What repo list?

What is the file name of the repo list?

[Sailor Enceladus]

@Lassar: Here's an example

1. Download the springflower.pet attached below and save it to your local-repositories/x86/packages-pet folder

2. Add an entry for it to say, Packages-puppy-noarch-official like this (middle line)

Code: Select all

snap2-4.26|snap2|4.26||Utility|168K||snap2-4.26.pet||snap2 snapshot backup||||
springflower|springflower|||BuildingBlock|228K||springflower.pet||new wallpaper||||
ssl-certificate-fix-0.0.1|ssl-certificate-fix|0.0.1||BuildingBlock|8K||ssl-certificate-fix-0.0.1.pet||ca-certificates config file||||

3. Then add an entry to DISTRO_PKGS_SPECS-yourdistro like this (middle line)

Code: Select all

yes|squashfs-tools4||exe,dev
yes|springflower||exe
no|ssh_gui||exe

4. Run ./2createpackages and write "springflower", then when ./3builddistro-Z is done you should have an extra wallpaper

(told ya the rootfs-packages way was simpler )

[Lassar]

Two changes needs to be made to the readme.txt file.

First:

"3. Build Puppy live-CD...you will also find the individual built files...

# ./3builddistro"

"./3builddistro" needs to be changed to "./3builddistro-Z"

Second:

Explanation needs to be added, about using "script 2>&1 | tee file.log".

This shows terminal output , and outputs terminal output to a file.

Example:

./3builddistro-Z 2>&1 | tee build-output.log

That way you can analyze the results of the output, and make changes to
DISTRO_PKGS_SPECS as needed.