Page 1 of 1

I want to build Ubuntu-Jammy64 similar to FossaPup64-9.5

Posted: Wed Nov 16, 2022 11:39 pm
by RyPuppy

I was recently able to build Ubuntu-22.04-Jammy64-x86_64-Kernel-5.15.x locally on my laptop with the help of @dimkr and others.

I would like to continue with my PET project and enhance the Ubuntu-Jammy64 pup to include all the features and packages that FossaPup64-9.5 had.

Could members who have had experience in building Pups please point me in the right direction...

Questions:
1. Where could I find the build Scripts used to build FossaPup64-9.5 ?
2. At the minimum having access to the main .conf files from the old-puppy will greatly help in understanding packages that needs to be built

Need help. Please post your suggestions...


Re: I want to build Ubuntu-Jammy64 similar to FossaPup64-9.5

Posted: Thu Nov 17, 2022 7:08 am
by peebee

You should find most info you need in:
puppy_fossapup64_9.5.sfs /var/packages

e.g. DISTRO_PKGS_SPECS woof-build.conf woof-installed-packages


Re: I want to build Ubuntu-Jammy64 similar to FossaPup64-9.5

Posted: Thu Nov 17, 2022 4:03 pm
by RyPuppy
peebee wrote: Thu Nov 17, 2022 7:08 am

You should find most info you need in:
puppy_fossapup64_9.5.sfs /var/packages

e.g. DISTRO_PKGS_SPECS woof-build.conf woof-installed-packages

@peebee Thanks for the helpful tips.


Re: I want to build Ubuntu-Jammy64 similar to FossaPup64-9.5

Posted: Fri Nov 18, 2022 1:04 am
by mikeslr

While you have access to FossaPup64-9.5's var/packages folder, it may be useful to copy the entire folder. It consists of text-readable files. Having it without having to file-browse into FossaPup64-9.5 again may save you some time. The content of each file in the 'builtin_files' folder is a list of files which were installed by that application and the location to which each such file was installed.


Re: I want to build Ubuntu-Jammy64 similar to FossaPup64-9.5

Posted: Fri Nov 18, 2022 1:44 am
by RyPuppy

@mikeslr Thank You. That's some very useful information you have provided.

I am running my build on FossaPup64.9.5 platform itself. With your approach, I will now be able to compare the newly built Pup when it is up & running with the old FossaPup.9.5.

To make it clear for others to follow:

Installation Info
FossaPup64-9.5 sda6:/FossaPup.9.5/
Ubuntu-Jammy64 sda6:/Ubuntu.Jammy64/
/var/packages sda6:/Packages.9.5 :

Directory : /var/packages (on FossaPup-9.5)

Code: Select all

$> ls -al /var/packages
total 21608
drwxr-xr-x  6 root root      320 Nov 17 17:46 .
drwxr-xr-x 44 root root      200 Nov 17 17:46 ..
drwxr-xr-x  2 root root    13300 Nov 17 17:44 builtin_files
drwxr-xr-x  2 root root    10780 Aug 25  2020 builtin_files-norm
drwxr-xr-x  2 root root     5986 Sep 17  2020 builtin_files-sml
-rw-r--r--  1 root root       12 Jun 25  2020 Custom_SFSs
-rw-r--r--  1 root root    28054 Sep 17  2020 devx-only-installed-packages
-rw-r--r--  1 root root     2024 Sep 17  2020 DISTRO_COMPAT_REPOS
-rw-r--r--  1 root root     2863 Sep 17  2020 DISTRO_PET_REPOS
-rw-r--r--  1 root root    57313 Nov 17 17:44 DISTRO_PKGS_SPECS
-rw-r--r--  1 root root    57313 Aug 25  2020 DISTRO_PKGS_SPECS-norm
-rw-r--r--  1 root root    55485 Jun 25  2020 DISTRO_PKGS_SPECS-sml
-rw-r--r--  1 root root      437 Nov 13 16:33 editorconfig_0.12.1-1.1.files
-rw-r--r--  1 root root     2946 Nov 13 12:01 firefox-77.0.1-x86_64.files
-rw-r--r--  1 root root        0 Nov 15 07:05 layers-installed-packages
-rw-r--r--  1 root root    27652 Nov 13 16:32 libperl5.30_5.30.0.files
-rw-r--r--  1 root root     9667 Nov 13 16:32 libtcl8.6_8.6.10+dfsg-1.files
-rw-r--r--  1 root root      269 Nov 13 16:32 libyaml-0-2_0.2.2-1.files
-rw-r--r--  1 root root    58008 Apr  5  2020 Packages-puppy-bionic64-official
-rw-r--r--  1 root root    22173 Nov 17 17:46 Packages-puppy-common64-official
-rw-r--r--  1 root root    17384 Oct  4  2021 Packages-puppy-fossa64-official
-rw-r--r--  1 root root    32263 Nov 17 17:46 Packages-puppy-noarch-official
-rw-r--r--  1 root root    62847 Nov 17 17:46 Packages-puppy-tahr64-official
-rw-r--r--  1 root root    23509 Nov 17 17:46 Packages-puppy-xenial64-official
-rw-r--r--  1 root root  4337583 Nov 17 17:46 Packages-ubuntu-focal-main
-rw-r--r--  1 root root   238250 Nov 17 17:46 Packages-ubuntu-focal-multiverse
-rw-r--r--  1 root root 15803548 Nov 17 17:46 Packages-ubuntu-focal-universe
-rw-r--r--  1 root root      270 Nov 14 20:09 patchelf_0.10.files
-rw-r--r--  1 root root     3854 Nov 17 17:46 PKGS_HOMEPAGES
-rw-r--r--  1 root root     1770 Nov 12 20:56 PKGS_MANAGEMENT
-rw-r--r--  1 root root     5651 Nov 13 16:32 rake_13.0.1-4.files
-rw-r--r--  1 root root      234 Nov 13 16:32 ruby_2.7+1.files
-rw-r--r--  1 root root     1957 Nov 13 16:32 ruby2.7_2.7.0.files
-rw-r--r--  1 root root      415 Nov 13 16:32 rubygems-integration_1.16.files
-rw-r--r--  1 root root     1186 Nov 13 16:32 ruby-minitest_5.13.0-1.files
-rw-r--r--  1 root root      646 Nov 13 16:32 ruby-net-telnet_0.1.1-2.files
-rw-r--r--  1 root root      873 Nov 13 16:32 ruby-power-assert_1.1.7-1.files
-rw-r--r--  1 root root     6721 Nov 13 16:32 ruby-test-unit_3.3.5-1.files
-rw-r--r--  1 root root      888 Nov 13 16:32 ruby-xmlrpc_0.3.0-2.files
-rw-r--r--  1 root root      314 Nov 15 07:06 squashfs-tools_4.4.files
-rw-r--r--  1 root root    11143 Nov 13 12:01 tor-browser-9.5-x86_64.files
-rw-r--r--  1 root root     5968 Nov 15 07:06 user-installed-packages
-rw-r--r--  1 root root     1712 Nov 13 16:32 vim-addon-manager_0.5.10.files
-rw-r--r--  1 root root     4389 Nov 13 16:32 vim-command-t_5.0.2-5-g7147ba9.files
-rw-r--r--  1 root root     2738 Nov 13 16:32 vim-common_8.1.2269.files
-rw-r--r--  1 root root      581 Nov 13 16:33 vim-editorconfig_0.3.3+dfsg-2.files
-rw-r--r--  1 root root      396 Nov 13 16:33 vim-gtk3_8.1.2269.files
-rw-r--r--  1 root root     2871 Nov 13 16:33 vim-gui-common_8.1.2269.files
-rw-r--r--  1 root root      387 Nov 13 16:32 vim-nox_8.1.2269.files
-rw-r--r--  1 root root    74225 Nov 13 16:32 vim-runtime_8.1.2269.files
-rw-r--r--  1 root root     6894 Sep 17  2020 woof-build.conf
-rw-r--r--  1 root root   407339 Nov 17 17:44 woof-installed-packages
-rw-r--r--  1 root root   407339 Aug 25  2020 woof-installed-packages-norm
-rw-r--r--  1 root root   231990 Jul 15  2020 woof-installed-packages-sml
-rw-r--r--  1 root root      620 Nov 13 16:32 xxd_8.1.2269.files

Grub2 - Entries
File : (sda5):/boot/grub/grub.cfg

Code: Select all

#===========================================================
menuentry '1. FossaPup.9.5 - Puppy Linux - [SDA6] - SAVE OPTION' {
  set root=(hd0,gpt6)

  echo '..... Loading Fossa Pup VMLINUZ .....'
  linux /FossaPup.9.5/vmlinuz psubdir=FossaPup.9.5 pmedia=usbflash
  
  echo '..... Loading Fossa Pup INITRD .....'
  initrd /FossaPup.9.5/initrd.gz
}
#===========================================================
menuentry '2. Ubuntu.Jammy64 - Puppy Linux - [SDA6] ' {
  set root=(hd0,gpt6)

  echo '..... Loading Ubuntu.Jammy64 : VMLINUZ .....'
  linux /Ubuntu.Jammy64/vmlinuz psubdir=/Ubuntu.Jammy64 pmedia=ataflash psave=sda6:/Ubuntu.Jammy64/RY.SAVE/
  
  echo '..... Loading Ubuntu.Jammy64 :  INITRD .....'
  initrd /Ubuntu.Jammy64/initrd.gz
}
#===========================================================

Thank You.


Re: I want to build Ubuntu-Jammy64 similar to FossaPup64-9.5

Posted: Fri Nov 18, 2022 2:58 pm
by mikeslr

Haven't had my 2nd cup of coffee yet. So haven't tried to digest your last post. But after my last it occurred to me that it's likely Jammy64 is created using a woof recipe more like VanillaDpup than the original Fossapup64. If so, it will lack a lot of the original Fossapup64's Right-Click and other tools. See my post here, https://www.forum.puppylinux.com/viewto ... 513#p69513.

A lot of manual labor went into creating Right-Click tools. It involves adding files to /root/.config/rox.sourceforge.net/OpenWith and sometimes /etc/xdg/rox.sourceforge.net/MIME-types. I never did get "Create a pet package" right so took the easy way out substituting "Make pet". And while sfs-load works there must be a better way which will display a nice icon. Decompressing the pet from the above link might be helpful in trying to recapture what philb666 had in the original Fossapup64.

If you do work in this area and figure out how to overcome the hurdles of SFS-Load and Create a pet" that I couldn't, let me know and I'll revise the RightClicks-Van pet (and change the title).


Re: I want to build Ubuntu-Jammy64 similar to FossaPup64-9.5

Posted: Sat Nov 19, 2022 1:27 am
by RyPuppy

I have been able to merge Packages from FossaPup64-9.5 into woof-CE build of Ubuntu-22.04-Jammy64 distro.

File DISTRO_PKGS_SPECS-ubuntu-jammy is being modified by changing field value from 'no' to 'yes' for the packages that existed in the old one but ignored in the latest woof-CE build.
yes|jwm|jwm|exe,dev,doc,nls

In some cases, I have to add lines as they do not exist in the new distro. It is a lengthy process as we are looking at 600-800 lines that needs to be reviewed.

Question:
1. How can I run the Build Scripts 0..1..2..3builddistro again & again ?
2. Is there a cleanup script or -REBUILD option build into the scripts ?
3. I have been deleting all of the following folders and starting fresh every time.

Code: Select all

local-repositories
woof-CE
woof-out_x86_64_x86_64_ubuntu_jammy64

4. Any pointers on how to bring about the look & feel of old FossaPup ?
5. Do I need manually figure out every .conf file and manually add ICONS, Commands etc to make this happen ?

I will post the Distro here once it is built with all the known FossaPup packages added to Ubuntu-Jammy Pup.

Also, I am thankful for the help I am getting in making this happen. I am learning... but it is still a long... long... way to go.


Re: I want to build Ubuntu-Jammy64 similar to FossaPup64-9.5

Posted: Sat Nov 19, 2022 7:43 am
by peebee

./0setup
./1download
./2createpackages for a single package or all packages
./2createpackages -downloaded for thoses packages just downloaded - but check /status/download_list is sane
./support/findpkgs to do a build check after a change

maybe the zz_ pets in http://distro.ibiblio.org/puppylinux/pe ... s-fossa64/ provide clues....

use petbuilds in preference to "yes" for e.g. jwm - that maybe why they are set to "no"