Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 17 Nov 2017, 21:23
All times are UTC - 4
 Forum index » Taking the Puppy out for a walk » Announcements
woof-CE needs you
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 64 of 79 [1182 Posts]   Goto page: Previous 1, 2, 3, ..., 62, 63, 64, 65, 66, ..., 77, 78, 79 Next
Author Message
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1278

PostPosted: Wed 31 May 2017, 12:44    Post subject: Re: failed to load ldlinux.c32  

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/viewtopic.php?p=948034#948034

shinobar says: "Intend to replace the remasterpup2, Puppy Live CD Remastering tool."
Back to top
View user's profile Send private message 
Billtoo


Joined: 07 Apr 2009
Posts: 3263
Location: Ontario Canada

PostPosted: Wed 31 May 2017, 20:24    Post subject: woof-CE needs you  

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.
gtkhash-1.1-i686.pet
Description 
pet

 Download 
Filename  gtkhash-1.1-i686.pet 
Filesize  101.27 KB 
Downloaded  38 Time(s) 
Screenshot.jpg
 Description   
 Filesize   57.47 KB
 Viewed   694 Time(s)

Screenshot.jpg

Back to top
View user's profile Send private message 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1278

PostPosted: Fri 02 Jun 2017, 12:33    Post subject:  

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 Wink
Back to top
View user's profile Send private message 
Lassar

Joined: 08 Jul 2014
Posts: 162

PostPosted: Fri 02 Jun 2017, 20:54    Post subject: Need info on how to add custom pet to woof-ce  

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?
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 3003
Location: Worcestershire, UK

PostPosted: Sat 03 Jun 2017, 03:41    Post subject: Re: Need info on how to add custom pet to woof-ce  

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

_________________
LxPup = Puppy + LXDE
Back to top
View user's profile Send private message Visit poster's website 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1278

PostPosted: Sat 03 Jun 2017, 11:35    Post subject:  

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.
Back to top
View user's profile Send private message 
Lassar

Joined: 08 Jul 2014
Posts: 162

PostPosted: Sat 03 Jun 2017, 16:53    Post subject:  

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:
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?

Last edited by Lassar on Sat 03 Jun 2017, 17:22; edited 1 time in total
Back to top
View user's profile Send private message 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1278

PostPosted: Sat 03 Jun 2017, 17:20    Post subject:  

Lassar wrote:
What am I doing wrong?

Nothing wrong per se, but you missed step #2 (the most annoying step probably Laughing ) in peebee's post.
Back to top
View user's profile Send private message 
Lassar

Joined: 08 Jul 2014
Posts: 162

PostPosted: Sat 03 Jun 2017, 17:29    Post subject:  

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,
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 3003
Location: Worcestershire, UK

PostPosted: Sat 03 Jun 2017, 18:06    Post subject:  

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

_________________
LxPup = Puppy + LXDE
Back to top
View user's profile Send private message Visit poster's website 
belham2

Joined: 15 Aug 2016
Posts: 1282

PostPosted: Sun 04 Jun 2017, 12:18    Post subject:  

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.
Back to top
View user's profile Send private message 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1278

PostPosted: Sun 04 Jun 2017, 15:52    Post subject:  

@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. Laughing
Back to top
View user's profile Send private message 
Lassar

Joined: 08 Jul 2014
Posts: 162

PostPosted: Sun 04 Jun 2017, 17:24    Post subject:  

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?
Back to top
View user's profile Send private message 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1278

PostPosted: Sun 04 Jun 2017, 17:51    Post subject:  

@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:
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:
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 Smile )
springflower.pet
Description  /usr/share/backgrounds/sanpati_1.jpg
pet

 Download 
Filename  springflower.pet 
Filesize  227.51 KB 
Downloaded  32 Time(s) 
Back to top
View user's profile Send private message 
Lassar

Joined: 08 Jul 2014
Posts: 162

PostPosted: Sun 04 Jun 2017, 18:24    Post subject: Changes to readme.txt  

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.

Last edited by Lassar on Sun 04 Jun 2017, 23:39; edited 2 times in total
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 64 of 79 [1182 Posts]   Goto page: Previous 1, 2, 3, ..., 62, 63, 64, 65, 66, ..., 77, 78, 79 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Taking the Puppy out for a walk » Announcements
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0657s ][ Queries: 14 (0.0126s) ][ GZIP on ]