woof-CE needs you

Message

smokey01 · #101 Post by **smokey01** » Tue 06 Oct 2015, 09:30

Guys it looks like you have given me a s*#t load of reading to do. Thanks for the links within the text. I will see if I can understand what it all means.

01micko · #102 Post by **01micko** » Tue 06 Oct 2015, 20:16

http://distro.ibiblio.org/puppylinux/te ... ko64/6060/

The iso, devx and kernel source is there.

Plenty of Bugs! All reproducible!!!

All commits have been made to woof. All packages to the best of my knowledge have been uploaded. I built this from the fdrv branch, so you may need to add frisbee and sfs_load to the PACKAGES_SPECS_TABLE var in DISTRO_PAKGS_SPECS file if you build from testing branch.. I forget.

There is one bug in the devx. fltk .. very minor. I have already used it to recompile a heap of broken packages then rebuild the iso, so it does mostly work.

Known issues: the drive icon thing, cups (aren't we a paperless society now?), xsane sees my freaking webcam [

], missing icons in menu, bacon is old (else the stupid 'welcome1stboot doesn't work), I forgot to add the ca-certificates (but in an earlier build I didn't so the pinstall.sh works in slacko), sylpheed is broken.. I used the wrong package!!!.. that's about all I know. There will be plenty more.

EDIT: CUPS and Xsane work!!!! Helps if you turn the effing printer on!!!!

Its a starting point.

Probably the worst obvious bug is the drive icons. You'll see.

(@smokey .. I left you a message in case I didn't get time to post this morning)

(@mavrothal - note that the BUILT_FROM_WOOF var is different from the latest commits to fdrv because I committed after build -- 5 commits behind, so it misses your PPM fixes).

Code: Select all

#One or more words that identify this distribution:
DISTRO_NAME='Slacko64 Puppy'
#version number of this distribution:
DISTRO_VERSION=6.0.6.0
#The distro whose binary packages were used to build this distribution:
DISTRO_BINARY_COMPAT='slackware64'
#Prefix for some filenames: exs: slacko64save.2fs, slacko64-6.0.6.0.sfs
DISTRO_FILE_PREFIX='slacko64'
#The version of the distro whose binary packages were used to build this distro:
DISTRO_COMPAT_VERSION='14.1'
#the kernel pet package used:
DISTRO_KERNEL_PET='Huge_Kernel'
BUILD_FROM_WOOF='fdrv;afd4722;2015-10-06 06:03:38 +1000'
DISTRO_TARGETARCH='x86_64'
DISTRO_XORG_AUTO='yes'
DISTRO_DB_SUBNAME='slacko6414.1'
#32-byte alpha-numeric ID-string appended to vmlinuz, puppy_slacko64_6.0.6.0.sfs, zdrv_slacko64_6.0.6.0.sfs and devx.sfs:
DISTRO_IDSTRING='s151006225926ZZZZ6.0.6.0XXXXXXXX'
#Puppy default filenames...
#Note, the 'SFS' files below are what the 'init' script in initrd.gz searches for,
#for the partition, path and actual files loaded, see PUPSFS and ZDRV in /etc/rc.d/PUPSTATE
DISTRO_PUPPYSFS='puppy_slacko64_6.0.6.0.sfs'
DISTRO_ZDRVSFS='zdrv_slacko64_6.0.6.0.sfs'
DISTRO_FDRVSFS='fdrv_slacko64_6.0.6.0.sfs'
DISTRO_ADRVSFS='adrv_slacko64_6.0.6.0.sfs'
DISTRO_YDRVSFS='ydrv_slacko64_6.0.6.0.sfs'
DISTRO_PUPPYDATE='Oct 2015'
#multiarch distros, such as Ubuntu, will have this. ex: /usr/lib/i386-linux-gnu, so DISTRO_ARCHDIR=i386-linux-gnu
DISTRO_ARCHDIR=''

Billtoo · #103 Post by **Billtoo** » Tue 06 Oct 2015, 21:15

01micko wrote:http://distro.ibiblio.org/puppylinux/te ... ko64/6060/
The iso, devx and kernel source is there.

It's looking good on my macmini so far, going to try out PPM next.

Thanks.

Edit: Haven't had a problem yet, downloaded some kdegames which also
downloads QT, added ca-certificates, compiled latest Smplayer and
Smtube.

slavvo67 · #104 Post by **slavvo67** » Wed 07 Oct 2015, 00:53

@01Mick0

If effing printer a puppy term?

I look forward to building Slacko this weekend; time permitting.

Thank you!

Slavvo67

mavrothal · #105 Post by **mavrothal** » Wed 07 Oct 2015, 03:58

01micko wrote:http://distro.ibiblio.org/puppylinux/te ... ko64/6060/
<snip>
All commits have been made to woof. All packages to the best of my knowledge have been uploaded. I built this from the fdrv branch
<snip>
Known issues: the drive icon thing,
<snip>
(@mavrothal - note that the BUILT_FROM_WOOF var is different from the latest commits to fdrv because I committed after build -- 5 commits behind, so it misses your PPM fixes).

Wow! A puppy that can really built from woof without tinkering?!?
You'll put all puppy builders out of job

How come there is no fdrv sfs? Is it with the "small" firmware package?

What "drive icon thing"?

(Latter: Ah ok. The mount-unmout thingy)

Do not bother about the PPM. Does not affect functionality.

Overall, although only tested in a VM. No issues. Straight to the desktop, with sound and network. All (few) apps I tried work as expected.
It could even updated the older slacko64 version (though the warning about running from CD during the update is a bit annoying. Was it always there?)

James C · #106 Post by **James C** » Wed 07 Oct 2015, 04:27

Quick manual frugal with just quick,basic testing......only obvious problem is the drive icons. Otherwise working well so far.

Code: Select all

# report-video
Report Video 1.3 - Tue 6 Oct 2015 on Slacko64 Puppy 6.0.6.0 - Linux 4.1.8 x86_64
 
Chip description:
  0.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)  
  oem: NVIDIA
  product: GT218 Board - 08720002 Chip Rev
 
X Server: Xorg  Driver used: nouveau

X.Org version: 1.14.3
  dimensions:    1440x900 pixels (381x238 millimeters)
  depth of root window:    24 planes 


   ...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz
#

01micko · #107 Post by **01micko** » Wed 07 Oct 2015, 08:05

Ok.. I just did ./1download with the default slacko-5.7 and the only crap is pmusic and pburn; indicating that I have everything locally. I'll attempt to resolve what is missing from the repo, but as for pburn and pmusic, well they are moving targets that I'm not going to track for a legacy build. (I didn't update *noarch).

Once missing packages are fixed, 5.7 should produce a sane build (well sane enough).

Next stop (for me) is slacko (32) based on 14.1 - and hopefully -current support. (but -current is a moving target too.. hence the build system

)

When slacko ( 32 - 14.1) is ready then I'm ready to merge testing to master. The status of slacko64 is *almost* ready.

666philb · #108 Post by **666philb** » Wed 07 Oct 2015, 08:27

a few missing libs

Code: Select all

# ./find_missing_libs
DIR /bin
DIR /usr/bin
/usr/bin/gresource:
	libelf.so.0 => not found
/usr/bin/gsx:
	libgtk-3.so.0 => not found
	libgdk-3.so.0 => not found
/usr/bin/memusagestat:
	libgd.so.2 => not found
/usr/bin/poppler-glib-demo:
	libgtk-3.so.0 => not found
	libgdk-3.so.0 => not found
/usr/bin/qv4l2:
	libQtGui.so.4 => not found
	libQtCore.so.4 => not found
/usr/bin/smbtorture:
	libpython2.7.so.1.0 => not found
	libpython2.7.so.1.0 => not found
	libpython2.7.so.1.0 => not found
/usr/bin/sylpheed:
	libgpgme.so.11 => not found
	libassuan.so.0 => not found
/usr/bin/x264:
	libavformat.so.55 => not found
	libavcodec.so.55 => not found
	libavutil.so.52 => not found
	libswscale.so.2 => not found
# 
also in the devx 
/usr/bin/cmake-gui:
	libQtGui.so.4 => not found
	libQtCore.so.4 => not found

01micko · #109 Post by **01micko** » Wed 07 Oct 2015, 08:32

If you are talking about slacko64 then these missing libs are intentional (well perhaps not all of them).

Some libs are hard dependencies and some are not. Slackware is a bit different

Iguleder · #110 Post by **Iguleder** » Wed 07 Oct 2015, 08:57

IMHO, we should open separate threads for the 32-bit and 64-bit Slacko releases, to attract more feedback, while issues in woof-CE are discussed here. That's a good way to make sure we actually fix problems in woof-CE, instead of using wonderful z_hacks PETs.

October and November are going to be very exciting for Puppy, I guess. 32/64 bit Slacko, tahrpup64 and Librepup in the pipeline

01micko · #111 Post by **01micko** » Wed 07 Oct 2015, 09:42

Iguleder wrote:IMHO, we should open separate threads for the 32-bit and 64-bit Slacko releases, to attract more feedback, while issues in woof-CE are discussed here. That's a good way to make sure we actually fix problems in woof-CE, instead of using wonderful z_hacks PETs.

October and November are going to be very exciting for Puppy, I guess. 32/64 bit Slacko, tahrpup64 and Librepup in the pipeline

I'll open a thread for each and all concerned when ready.. which will be soon.

I have just fixed legacay slacko-5.7 and bumped the version to 5.7.1, so this *should* now do a sane build from slackware-14.0.

One left, then I'm good. (slackware 32 based on 14.1 [ - then -current support ] )

Billtoo · #112 Post by **Billtoo** » Wed 07 Oct 2015, 15:30

@01micko

I did another manual frugal install to use on my Gateway desktop.
I installed the proprietary nvidia driver,after setting up and exiting
nvidia-settings it gave errors but running smplayer full screen is
looking good.

Report Video 1.3 - Wed 7 Oct 2015 on Slacko64 Puppy 6.0.6.0 - Linux 4.1.8 x86_64

Chip description:
0.0 VGA compatible controller: NVIDIA Corporation GF110 [GeForce GTX 560 Ti OEM] (rev a1)
oem: NVIDIA
product: GF110 Board - 12630002 Chip Rev

X Server: Xorg Driver used: nvidia

X.Org version: 1.14.3
dimensions: 3840x1080 pixels (1204x343 millimeters)
depth of root window: 24 planes

--------------------------------------------------------------------------------------------------------

Edit: I did another manual frugal install to use on a pc with ati
graphics:

Report Video 1.3 - Wed 7 Oct 2015 on Slacko64 Puppy 6.0.6.0 - Linux 4.1.8 x86_64

Chip description:
0.0 VGA compatible controller: AMD/ATI [Advanced Micro Devices, Inc.] Redwood PRO [Radeon HD 5570]
oem: ATI ATOMBIOS
product: REDWOOD 01.00

X Server: Xorg Driver used: radeon

X.Org version: 1.14.3
dimensions: 1920x1080 pixels (508x285 millimeters)
depth of root window: 24 planes

Hardware acceleration is working, is working on the macmini as well
(intel graphics).
I'm guessing it is working with nouveau as well but I'm too lazy atm to
test that

Ted Dog · #113 Post by **Ted Dog** » Wed 07 Oct 2015, 16:39

Some of us are waiting for Slacko64 to drop to work on WolfCE, so please be kind to posters.

zigbert · #114 Post by **zigbert** » Wed 07 Oct 2015, 18:47

I have looked at jwm_config. Tonight, I've got it running with jwm 2.3.2 without crashing - it's a start

. There is still more to do before it is 100%. I'll continue when time allows me...

gcmartin · #115 Post by **gcmartin** » Wed 07 Oct 2015, 23:28

WOOFCE continues to mature and advance.

Not sure if this is the a good place to bring this up, but, is touch ability an item that is addressed in WOOFCE? Is there any approach that devs need to be aware of?

01micko · #116 Post by **01micko** » Thu 08 Oct 2015, 08:40

@smokey01 and @Ted Dog and others interested in building Slacko/Slacko64

Rather than me upload another testing iso, why don't you build it yourselves? Slacko64 I uploaded already is sane enough to build a distro. It has bugs, but the object of the exercise is to download it, then update woof to the latest testing branch and build it!

This will work for slacko (32 bit) also. You can use slacko 5.7 or 5.9.3, doesn't matter. If you have git troubles, update the Patches repo and grab the ca-certificates. This also applies to Slacko64 as I forgot to include them (but they are in the new configuration).

I have just pushed all changes and (hopefully) all updated packages are uploaded to Ibiblio. Please let me know of any issues.

Have fun with that!

anikin · #117 Post by **anikin** » Thu 08 Oct 2015, 11:33

gcmartin wrote:Not sure if this is the a good place to bring this up, but, is touch ability an item that is addressed in WOOFCE? Is there any approach that devs need to be aware of?

Touch has nothing to do with woof - it's a kernel build option.

gcmartin wrote:WOOFCE continues to mature and advance.

Really? How do you know? Have you managed already to build a pup using woof-CE?

gyro · #118 Post by **gyro** » Thu 08 Oct 2015, 12:41

Hi,
Is there a place in Woof-CE to store the source code of compiled utilities?
e.g. "freememapplet_tray.c" and it's "compile" script.
gyro

mavrothal · #119 Post by **mavrothal** » Thu 08 Oct 2015, 13:21

gyro wrote:Hi,
Is there a place in Woof-CE to store the source code of compiled utilities?
e.g. "freememapplet_tray.c" and it's "compile" script.
gyro

Not really. There is some source code in woof-CE/woof-code/support but BK used to keep all source code in bkhome.org/sources. In addition, woof building does not have any compiling step.
However, the puppylinux-woof-CE project has several sub-projects besides woof-CE, so a "puppy-sources" git could be opened there.
Alternatively the petbuilds subproject could also hold sources and compile scripts.
Finally, a sources directory could be open in woof-CE and build scripts modified to compile at build time if no binary available. But this can be very messy.
I would go with a sub-project repo.
What do you think?

gyro · #120 Post by **gyro** » Thu 08 Oct 2015, 18:45

mavrothal wrote:What do you think?

I think that having a utilities sources directly stored in it's own directory in a "puppy-sources" sub-project, would be a step forward from storing it as a "tar.bz2" on "http://distro.ibiblio.org/puppylinux/sources/".
I assume that "petbuilds" scripts would be readily able to access such source files.

gyro

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

woof-CE needs you

woof-CE needs you