(old)Puppy Linux Discussion Forum

Lassar wrote: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."

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.

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

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?

Lassar wrote: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.....

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.

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:
What am I doing wrong?

Lassar wrote:What am I doing wrong?

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

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,

Lassar wrote: 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

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.

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

peebee wrote: ...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?

@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)
3. Then add an entry to DISTRO_PKGS_SPECS-yourdistro like this (middle line)
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 )

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.

What is the best way to modify DISTRO_PKGS_SPECS as far as dependencies are concerned.

DISTRO_PKGS_SPECS-ubuntu-xenial mentions vlc, and mplayer package.

Example:

yes|speex|libspeex1,libspeex-dev,libspeexdsp1,libspeexdsp-dev|exe,dev,doc,nls| #needed by mplayer, vlc. note, some apps only need libspeex1, others need both.

Do I say yes as kodi might need them, or do I say no to these and let the
thorough dependency check warn me about dependencies needed.

I want to minimize the size of the puppy.

Which is best?

On doing a thorough dependency check.

Will doing a thorough dependency check warn me about packages, that I do not need.

Will doing a thorough dependency check warn me about packages, that I need.

What is the best way of doing this?

Lassar wrote:Two changes needs to be made to the readme.txt file.

First:

"3. Build Puppy live-CD
This gets built in a directory named 'sandbox3' and as well as the live-CD iso file you will also find the individual built files and the 'devx' file.

# ./3builddistro"

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

The "NOTE June. 18, 2014" at the bottom talks about the switch to 3builddistro-Z in more detail. I think that's an interesting approach that works, and punishes people who don't read the whole thing and rewards those who do.

Sailor Enceladus wrote:

Lassar wrote:Two changes needs to be made to the readme.txt file.

First:

"3. Build Puppy live-CD
This gets built in a directory named 'sandbox3' and as well as the live-CD iso file you will also find the individual built files and the 'devx' file.

# ./3builddistro"

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

The "NOTE June. 18, 2014" at the bottom talks about the switch to 3builddistro-Z in more detail. I think that's an interesting approach that works, and punishes people who don't read the whole thing and rewards those who do.

./3builddistro is just plain wrong, inaccurate, and confuses people.

We want to keep the readme.txt truthful & accurate.

I tried another Slacko 5.7.1 build. Some things in it are pretty old by today's standards, like the mksquashfs versions don't understand what "-comp xz" is, but it might make a fun play thing. 2014 slacko with 2017 woof-ce and security updates. Haha.

Sailor,

Didn't you mention this bug somewhere? I just encountered it today:

http://murga-linux.com/puppy/viewtopic. ... 828#956828

Am I remembering correctly?? I know someone wrote about in the past few days, and I thought it was you. I'm looking for a solution, if there is one.

Thanks!