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 Mon 27 May 2019, 09:31
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
alternative puppy build system
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 19 of 25 [363 Posts]   Goto page: Previous 1, 2, 3, ..., 17, 18, 19, 20, 21, 22, 23, 24, 25 Next
Author Message
musher0

Joined: 04 Jan 2009
Posts: 14165
Location: Gatineau (Qc), Canada

PostPosted: Wed 15 May 2019, 21:25    Post subject:  

This is what my basesfs now looks like:
Code:
# ubuntu/debian puppy basesfs pkglist
#
# generic commands: %exit %include %makesfs %import
# special package commands: %get_pkgs_by_priority %addbase %addpkg %bblinks %remove %repo %lock %cutdown
# installer commands: %bootstrap %dpkg %dpkgchroot %depend %nodepend %reinstall %dpkg_configure
# startup default: bootstrap, nodepend
#
# extra param for commands, params can be quoted
# %include        include-file
# %makesfs        output.sfs [squashfs-param]
# %pkg_by_prio    priority ["inclusion-egrep"] ["exclusion-egrep"]
# %bblinks        [nousr]
# %remove         pkgname ...
# %repo           url version sections pkgdb
# %addpkg         pkgname ...
# %reinstall      pkgname ...
# %dpkg_configure configure flags
# %lock           pkgname ...
# %cutdown        [all doc gtkdoc nls cache dev]
# %import         dir ...
#
# %symlink        source target
# %rm             file ... (-rf flag is always used)
# %mkdir          dir ... (-p flag is always used)
# %touch          file ...
# % %chroot         command ...
#
# start with %pkgs_by_prio required. Otherwise start with libc6.
#

# essential packages
%pkgs_by_priority "required" ".*lib.*|^tzdata|^bash|^dash|^lsb-base|^ncurses.*|^bsdutils|^kmod|^mount|^insserv|^mount|^sysvinit-utils|^procps|^makedev" "^klibc|.*plymouth.*|mountall"
#%pkgs_by_priority "required"
#%dpkg             # use dpkg installer instead of bootstrap
#%dpkgchroot       # use dpkg-chroot installer instead of bootstrap
%depend            # turn on dependency
coreutils
grep
# gawk
sed
tar
gzip
cpio
lsof
dialog
gettext
unzip
zip
rsync
procps
autofs
pmount

# extra packages
screen             # useful for debugging
file               # for checking file types
locales            # locale files
util-linux

# xorg packages
%nodepend          # disable dep for udev, otherwise brings loads of dependencies
libkmod2           # debian needs this
udev
%depend            # enable dep for xorg, makes life simpler for us
xserver-xorg
xinit
x11-utils
x11-xserver-utils
fonts-dejavu-core  # standard font
kbd

# debian dependencies
libxcb-shm0

# window managers etc
jwm
icewm
rox-filer          # this will pull-in gtk2
rxvt-unicode
mlterm
bmpanel2
xdotool
wmctrl
gtk-chtheme

# extra libs
librsvg2-2
%nodepend          # librsvg2-bin will pull gtk3 if told not to.
librsvg2-bin       # to convert puppy SVG icons to png
%depend
librsvg2-common    # pixbuf loaders, so GTK2 can shows SVG icons
#libgnome-menu2    # for jwm-xdgmenu, openbox-xdgmenu, etc

# apps
mtpaint
leafpad
links2
htop
joe
geany
mc
renameutils
htpdate
gnumeric
mpv
mksquashfs
unsquashfs
xlock
xcalc
xclock
qiv
sqlite3
ted

# apt and friends - with its run-time dependencies (among others)
diffutils
util-linux
e2fsprogs
findutils
perl-base
module-init-tools
libatm1
passwd
isc-dhcp-common
iproute2
isc-dhcp-client
psmisc
libxtables10
gcc-7-base
apt-utils
apt
gnupg
debian-keyring
%dummy init-system-helpers dbus-user-session # make apt happy

# enable proper support for package signing
%dpkgchroot
%reinstall debian-keyring apt
%bootstrap

# network tools to make SNS happy
ifplugd
dhcpcd5
wireless-tools
wpasupplicant

# fixes for apt-get: re-install perl-base and xserver-xorg-core with dpkg
%dpkgchroot
%reinstall perl-base xserver-xorg-core
%bootstrap         # switch back to bootstrap installer - faster

synaptic # this will pull-in gtk3, systemd, etc
dbus

# puppy specific packages
#%repo http://jamesbond3142.no-ip.org/puppy-extra puppy main Packages.gz
xdialog            # note: only i386 arch available
gtkdialog          # note: only i386 arch available

# final steps
# remove extremely toxic packages, then setup the dummy
%remove initscripts ifupdown sysv-rc upstart mountall login
%dummy  initscripts ifupdown sysv-rc upstart mountall login

# these useless packages got pulled by apt-get -f install, so prevent it from getting installed
%rm /sbin/init # don't use systemd-init, use busybox one instead
%remove plymouth libplymouth2 plymouth-theme-ubuntu-text
%dummy  plymouth libplymouth2 plymouth-theme-ubuntu-text
%remove busybox-initramfs initramfs-tools-bin klibc-utils initramfs-tools
%dummy  busybox-initramfs initramfs-tools-bin klibc-utils initramfs-tools
%dummy  adduser base-files

# install busybox and its symlinks, fallback for missing utilities
busybox-static
%bblinks
%remove lzop less awk

# install extra built-in packages
%addpkg pthemes
%addpkg rox-filer-data

# install puppy-base - MUST BE LAST - unless overriding puppy-base
%dpkg_configure --force-all -a
%addbase
%addpkg debian-setup # specific debian setup, overriding puppy-base
%lock puppy-base puppy-base-arch libc6 # example: never update puppy base and libc6

%addpkg james-staging # temporary area to changes before they get merged to rootfs

# cutdown the size
# %cutdown doc gtkdoc nls # all # maximum cutdown
# NON. NLS nécessaire pour un Puppy international.

# make the sfs (optional)
# %makesfs iso/iso-root/puppy.sfs -noappend -all-root -b 1048576 -comp xz -Xdict-size 100%
# Orig. : # -comp gzip -Xcompression-level 1

_________________
musher0
~~~~~~~~~~
Je suis né pour aimer et non pas pour haïr. (Sophocle) /
I was born to love and not to hate. (Sophocles)
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 3349
Location: The Blue Marble

PostPosted: Wed 15 May 2019, 22:40    Post subject:  

musher0 wrote:
Hello.

Does anybody know where to find the localized ISO-8859-* and UTF-8, such as
fr_CA.UTF_8,
es_AR.UTF-8.

Jamesbond's woof-Next already has a few: en_US, en_AU.
If you have friends that use internationalized Linuxes, please circulate this request, I'd
appreciate it.

Look into the file woof-code/rootfs-packages/debian-setup/pinstall.sh
(this file is part of the tarball from woof-next).

At the bottom of this file, you will see
Code:
echo Generating locale files
chroot . /usr/bin/localedef --no-archive -i en_US en_US
chroot . /usr/bin/localedef --no-archive -i en_AU en_AU
chroot . /usr/bin/localedef --no-archive -i en_US -f UTF-8 en_US.UTF-8
chroot . /usr/bin/localedef --no-archive -i en_AU -f UTF-8 en_AU.UTF-8


Add other locales as needed.

Ref: https://github.com/puppylinux-woof-CE/woof-CE/blob/woof-next/woof-code/rootfs-packages/debian-setup/pinstall.sh

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.
Back to top
View user's profile Send private message 
wanderer

Joined: 20 Oct 2007
Posts: 1063

PostPosted: Wed 15 May 2019, 22:59    Post subject:  

hi all

so i assume

s243a is building a woof-next from devuan and tinycore with slaz components

musher0 is building a woof-next from debian sid

and foxpup is build a woof-next from slackware

am i right

wanderer
Back to top
View user's profile Send private message 
s243a

Joined: 02 Sep 2014
Posts: 1773

PostPosted: Wed 15 May 2019, 23:14    Post subject:  

wanderer wrote:
hi all

so i assume

s243a is building a woof-next from devuan and tinycore with slaz components

musher0 is building a woof-next from debian sid

and foxpup is build a woof-next from slackware

am i right

wanderer


Just devuan and tinycore in my test, no SliTaZ on this test.

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
wanderer

Joined: 20 Oct 2007
Posts: 1063

PostPosted: Wed 15 May 2019, 23:28    Post subject:  

thanks s243a

wanderer
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 14165
Location: Gatineau (Qc), Canada

PostPosted: Thu 16 May 2019, 00:06    Post subject:  

wanderer wrote:
hi musher0

welcome back

we missed you

we wont forget about you multilingual guys

wanderer
Thanks much, wanderer. Goes right to my heart!
( Sorry for being so kitch, but I'm like that sometimes! )

_________________
musher0
~~~~~~~~~~
Je suis né pour aimer et non pas pour haïr. (Sophocle) /
I was born to love and not to hate. (Sophocles)
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 14165
Location: Gatineau (Qc), Canada

PostPosted: Thu 16 May 2019, 00:07    Post subject:  

wanderer wrote:
hi all

so i assume

s243a is building a woof-next from devuan and tinycore with slaz components

musher0 is building a woof-next from debian sid

and foxpup is build a woof-next from slackware

am i right

wanderer
Ahem, wanderer.
That would more correctly be:
" musher0 is ( trying to ) build a woof-next from debian sid." Laughing

BFN.

_________________
musher0
~~~~~~~~~~
Je suis né pour aimer et non pas pour haïr. (Sophocle) /
I was born to love and not to hate. (Sophocles)
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 14165
Location: Gatineau (Qc), Canada

PostPosted: Thu 16 May 2019, 00:20    Post subject:  

jamesbond wrote:
musher0 wrote:
Hello.

Does anybody know where to find the localized ISO-8859-* and UTF-8, such as
fr_CA.UTF_8,
es_AR.UTF-8.

Jamesbond's woof-Next already has a few: en_US, en_AU.
If you have friends that use internationalized Linuxes, please circulate this request, I'd
appreciate it.

Look into the file woof-code/rootfs-packages/debian-setup/pinstall.sh
(this file is part of the tarball from woof-next).

At the bottom of this file, you will see
Code:
echo Generating locale files
chroot . /usr/bin/localedef --no-archive -i en_US en_US
chroot . /usr/bin/localedef --no-archive -i en_AU en_AU
chroot . /usr/bin/localedef --no-archive -i en_US -f UTF-8 en_US.UTF-8
chroot . /usr/bin/localedef --no-archive -i en_AU -f UTF-8 en_AU.UTF-8


Add other locales as needed.

Ref: https://github.com/puppylinux-woof-CE/woof-CE/blob/woof-next/woof-code/rootfs-packages/debian-setup/pinstall.sh

Thanks, jamesbond.

However, I think this is impractical. I cannot know in advance if an Italian, an Austrian, a
Finlander, or a Brazilian, etc., will be using this Pup, can I?

Or we create the whole lot of them? Not practical either, I think, because that may take
a lot of space. Although, they are not such big files, and if that is what it takes...

BFN.

_________________
musher0
~~~~~~~~~~
Je suis né pour aimer et non pas pour haïr. (Sophocle) /
I was born to love and not to hate. (Sophocles)
Back to top
View user's profile Send private message 
s243a

Joined: 02 Sep 2014
Posts: 1773

PostPosted: Thu 16 May 2019, 00:37    Post subject:  

musher0 wrote:
jamesbond wrote:
musher0 wrote:
Hello.

Does anybody know where to find the localized ISO-8859-* and UTF-8, such as
fr_CA.UTF_8,
es_AR.UTF-8.

Jamesbond's woof-Next already has a few: en_US, en_AU.
If you have friends that use internationalized Linuxes, please circulate this request, I'd
appreciate it.

Look into the file woof-code/rootfs-packages/debian-setup/pinstall.sh
(this file is part of the tarball from woof-next).

At the bottom of this file, you will see
Code:
echo Generating locale files
chroot . /usr/bin/localedef --no-archive -i en_US en_US
chroot . /usr/bin/localedef --no-archive -i en_AU en_AU
chroot . /usr/bin/localedef --no-archive -i en_US -f UTF-8 en_US.UTF-8
chroot . /usr/bin/localedef --no-archive -i en_AU -f UTF-8 en_AU.UTF-8


Add other locales as needed.

Ref: https://github.com/puppylinux-woof-CE/woof-CE/blob/woof-next/woof-code/rootfs-packages/debian-setup/pinstall.sh

Thanks, jamesbond.

However, I think this is impractical. I cannot know in advance if an Italian, an Austrian, a
Finlander, or a Brazilian, etc., will be using this Pup, can I?

Or we create the whole lot of them? Not practical either, I think, because that may take
a lot of space. Although, they are not such big files, and if that is what it takes...

BFN.


So then we need to add the %babblefish directive?

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 1773

PostPosted: Thu 16 May 2019, 00:40    Post subject:  

I think I found an error.

In

Code:

### prepare critical dirs
prepare_dirs() {
   rm -rf $CHROOT_DIR
   mkdir -p $REPO_DIR $CHROOT_DIR $CHROOT_DIR/$APT_SOURCES_DIR $CHROOT_DIR/$APT_PKGDB_DIR
   for p in info parts alternatives methods updates; do
      mkdir -p $CHROOT_DIR/$ADMIN_DIR/$p
   done
   ! [ -e $CHROOT_DIR/$ADMIN_DIR/status ]    && echo > $CHROOT_DIR/$ADMIN_DIR/status
   ! [ -e $CHROOT_DIR/$ADMIN_DIR/available ] && echo > $CHROOT_DIR/$ADMIN_DIR/available
   
   if ! [ -e helpers ]; then
      mkdir -p helpers
      (cd helpers; ln -sf $(which true) update-rc.d)
   fi
   PATH=$(pwd)/helpers:$PATH
   > $TRACKER
}


around line 55 of deb-build.sh, I don't think there should be a slash between the $CHROOT_DIR and $ADMIN_DIR

When I run the command:
Code:

bash -x ./build-sfs.sh 2>&1 | tee build-sfs.log

I get in my log file:
Code:

+ ADMIN_DIR=/var/lib/dpkg
...
+ prepare_dirs
+ rm -rf chroot-ascii-x86
+ mkdir -p repo-ascii-x86 chroot-ascii-x86 chroot-ascii-x86//etc/apt/sources.list.d chroot-ascii-x86//var/lib/apt/lists
+ for p in info parts alternatives methods updates
+ mkdir -p chroot-ascii-x86//var/lib/dpkg/info
+ for p in info parts alternatives methods updates
+ mkdir -p chroot-ascii-x86//var/lib/dpkg/parts
+ for p in info parts alternatives methods updates
+ mkdir -p chroot-ascii-x86//var/lib/dpkg/alternatives
+ for p in info parts alternatives methods updates
+ mkdir -p chroot-ascii-x86//var/lib/dpkg/methods
+ for p in info parts alternatives methods updates
+ mkdir -p chroot-ascii-x86//var/lib/dpkg/updates
+ '[' -e chroot-ascii-x86//var/lib/dpkg/status ']'
+ echo
+ '[' -e chroot-ascii-x86//var/lib/dpkg/available ']'


anyway, I'm going to make the change in my fork Smile

Edit: This actually impacts quite a few lines:
https://github.com/s243a/woof-CE/commit/a049ca9f544b540edba6595250ce5b2da73c6665#diff-4804c0f9d8f7bc41c2232bc3deb1505b (presuming I'm correct)

_________________
Find me on minds and on pearltrees.

Last edited by s243a on Thu 16 May 2019, 02:13; edited 2 times in total
Back to top
View user's profile Send private message Visit poster's website 
musher0

Joined: 04 Jan 2009
Posts: 14165
Location: Gatineau (Qc), Canada

PostPosted: Thu 16 May 2019, 00:41    Post subject:  

Hi all.

A couple of things:

Is udev a nuisance or a help?
jamesbons mentions something about Xorg importing a lot of dependencies if we don't use udev.
Code:
# xorg packages
%nodepend          # disable dep for udev, otherwise brings loads of dependencies
libkmod2           # debian needs this
udev
%depend            # enable dep for xorg, makes life simpler for us
xserver-xorg
xinit
x11-utils
x11-xserver-utils
fonts-dejavu-core  # standard font
( Lines 60 to 70 in my basesfs )
I downloaded and installed k 4.14 32-bit by (I can't remember his nickname ATM, but
he's a German-American fellow, and assistant-moderator ). Ah, it's come back to me:
"rockedge" is his nickname on this forum.

Last 32-bit kernel on StemSee's kernels thread, it seems.

Glitches:
-- It doesn't recognize former pupsave;

-- It asks me in the initial black console keyboard and video card. I'm using an old Nvidia
128 Mg card, so I answer "nouveau".

-- Then keyboard and mouse freeze at set-up panel ( languages, keyboards, TZ's ) on
desktop.

That did not happen with StemSee's k 4.4.1.

Does that have anything to do with udev? Should I rather let the X dependencies install
and comment out udev?

~~~~~~~~~~~

One other thing, please: woof-Next only has one single initrd.gz for all kernels, yes?

Would it be different if I compiled a kernel through the kernel-kit? Which I do not want to do if I can avoid it.

BFN.

_________________
musher0
~~~~~~~~~~
Je suis né pour aimer et non pas pour haïr. (Sophocle) /
I was born to love and not to hate. (Sophocles)
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 14165
Location: Gatineau (Qc), Canada

PostPosted: Thu 16 May 2019, 00:45    Post subject:  

@s243a
"babbelfish directive"? Sorry, jo no comprendo. Like in the Tower of Babbel story in the
Bible -- with a trout or a sardine, perhaps? Laughing

_________________
musher0
~~~~~~~~~~
Je suis né pour aimer et non pas pour haïr. (Sophocle) /
I was born to love and not to hate. (Sophocles)
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 14165
Location: Gatineau (Qc), Canada

PostPosted: Thu 16 May 2019, 01:02    Post subject:  

wanderer wrote:
hi musher0


you might like this new system
it has a bunch of window managers besides jwm


wanderer

Where? Where? ( Shucks, no "Drooling" icon on this forum! )

Seriously, I'd like to include waimea as a WM, but just my luck, there is no
Debian package for it.

It won't tell you much, but waimea is peklwm's "uncle", so to speak. It's in
the lineage from aewm to pekwm.

Plus it has transparency and a lot of other nice features that jwm doesn't have,
yan-han-han!

Would it be kosher for me to include my compilation of it in the "skeleton"?

BFN.

_________________
musher0
~~~~~~~~~~
Je suis né pour aimer et non pas pour haïr. (Sophocle) /
I was born to love and not to hate. (Sophocles)

Last edited by musher0 on Thu 16 May 2019, 16:23; edited 1 time in total
Back to top
View user's profile Send private message 
s243a

Joined: 02 Sep 2014
Posts: 1773

PostPosted: Thu 16 May 2019, 01:08    Post subject:  

musher0 wrote:
wanderer wrote:
hi musher0


you might like this new system
it has a bunch of window managers besides jwm


wanderer

Where? Where? ( Shucks, no "Drooling" icon on this forum! )

Seriously, I'd like to include waimea as a WM, but just my luck, there is no Debian
package for it.

It won't tell you much, but waimea is peklwm's "uncle", so to speak. It's in the lineage from aewm to pekwm.

Plus it has transparency and a lot of other nice features that jwm doesn't have,
yan-han-han!

Would it be kosher for me to include my compilation of it in the "skeleton"?

BFN.


You can get transparencies in jwm but I don't like them.

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 1773

PostPosted: Thu 16 May 2019, 12:22    Post subject:  

So I tried chrooting into the rootfs that was built by woof-next to troubleshoot issues with sc0ttman's puppy-PKG. I get the error:
Code:

+ chroot /mnt/home/git_projects/woof-next/workdir/chroot-ascii-x86 /bin/sh
FATAL: kernel too old

I find the following info on the gento mailing list:
Quote:

It means your running kernel is too old for the version of glibc in your
chroot. Either upgrade your kernel or downgrade glibc in the chroot. You can
probably do the latter by downloading an older stage3 e.g. 2006.0 (or
possibly 2005.x...).

https://lists.gt.net/gentoo/user/142867
My version of dupup strech is running 4.1.48. I suppose I'll try upgrading to the next size up in kernals and see what happens.

As a side note, I recall reading on this forum that kernal support is based on how you compile glibc and it is possible to compile glibc for a large range of kernals.

Edit: Here is the post that notes that one can compile glibc for a wide range of kernals:

Quote:

As Iguleder points out, the situation with the latest kernel and Xorg drivers is inter-related -this was not always so.
But, with glibc it is that glibc is compiled to accept a range of kernel versions. The kernel doesn't know or care anything about glibc -it's the libc(glibc,musl,uclibc,..) which has to understand the kernel.

http://www.murga-linux.com/puppy/viewtopic.php?p=742262#742262

Now this is interesting because if puppy supports a wider ranger of kernels than tinycore, then perhaps puppy has advantages (beyond just more features) over tinycore for old hardware.

Edit 2: I see that tinycore 9 uses kernal 4.14.10, so maybe I'll try updating my dpup strech to this kernal.

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 19 of 25 [363 Posts]   Goto page: Previous 1, 2, 3, ..., 17, 18, 19, 20, 21, 22, 23, 24, 25 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
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.0620s ][ Queries: 13 (0.0075s) ][ GZIP on ]