TazPuppy 5.0 rc2
-
- Posts: 98
- Joined: Mon 17 Oct 2016, 05:11
That was nice @thinkpadfreak
Take note next tazpuppy release will be more bleeding edge. Because the build kit used for building tazpuppy was revised and using a new build approach. The tazpuppy builder will now use chroot and use the stock tazpkg to perform modifications (adding and removing packages) in slitaz rootfs for tazpuppy prior to patching. This will provide even more reliable filesystem structure and accurate package management in tazpuppy. Also it will allow to include pet package installation in the future.
I hope that it will succeed
Take note next tazpuppy release will be more bleeding edge. Because the build kit used for building tazpuppy was revised and using a new build approach. The tazpuppy builder will now use chroot and use the stock tazpkg to perform modifications (adding and removing packages) in slitaz rootfs for tazpuppy prior to patching. This will provide even more reliable filesystem structure and accurate package management in tazpuppy. Also it will allow to include pet package installation in the future.
I hope that it will succeed
TazPuppy Beta 15 released
Changes:
* Build from tazpup builder 5.0
* Recharge function on tazpkg works if there is an active network connection
* Added support for loading Slax and Porteus modules
Download: https://drive.google.com/open?id=1abm3t ... pcJMYq8SwT
MD5 Checksum: 4d6e539ba0640fa16cdca31ea74c3298
Build kit: https://drive.google.com/file/d/171UYw- ... sp=sharing
Changes:
* Build from tazpup builder 5.0
* Recharge function on tazpkg works if there is an active network connection
* Added support for loading Slax and Porteus modules
Download: https://drive.google.com/open?id=1abm3t ... pcJMYq8SwT
MD5 Checksum: 4d6e539ba0640fa16cdca31ea74c3298
Build kit: https://drive.google.com/file/d/171UYw- ... sp=sharing
On my latest experiment. I try to modify a copy tazpkg install script to allow installation of pet packages natively but instead of petget/ppm method, it uses tazpkg method of installation and uninstallation. also it allows to install dependencies from slitaz repo
tazpkg has added suppression features which skips some functions by placing a designated lock file on /tmp. It was very useful in tazpup builder.
Building tazpup from local and online is now integrated in a single script. (requires Xdialog)
tazpkg has added suppression features which skips some functions by placing a designated lock file on /tmp. It was very useful in tazpup builder.
Building tazpup from local and online is now integrated in a single script. (requires Xdialog)
TazPuppy Beta 16 released
Changes:
* NATIVE PET PACKAGE SUPPORT. No more package conversion needed. pet packages was installed the same as slitaz package. It can uninstalled it using tazpkg or even repack it as slitaz package
* Improvements on tazpkg
* Build from tazpup builder 5.1
* More fixes
Changes in TazPup Builder:
* Now supports different Slitaz ISO images aside slitaz-rolling-core.iso
* It can now include custom pet packages for building tazpuppy
* Single script and more user friendly
Download: https://drive.google.com/file/d/1V9ouEX ... sp=sharing
MD5 Checksum: 0ee4f57a2c6c5666390eac855312296b
Build kit: https://drive.google.com/file/d/1pP_OVZ ... sp=sharing
Changes:
* NATIVE PET PACKAGE SUPPORT. No more package conversion needed. pet packages was installed the same as slitaz package. It can uninstalled it using tazpkg or even repack it as slitaz package
* Improvements on tazpkg
* Build from tazpup builder 5.1
* More fixes
Changes in TazPup Builder:
* Now supports different Slitaz ISO images aside slitaz-rolling-core.iso
* It can now include custom pet packages for building tazpuppy
* Single script and more user friendly
Download: https://drive.google.com/file/d/1V9ouEX ... sp=sharing
MD5 Checksum: 0ee4f57a2c6c5666390eac855312296b
Build kit: https://drive.google.com/file/d/1pP_OVZ ... sp=sharing
New clean frugal install to Sandisk 32GB Flash Drive. All working well after initial save folder creation.
I attempted to install an inxi pet. When attempting to install as tux, a message about some packages requiring root access, I clicked Install and a blank tazpet Puppy Package Action dialogue window was displayed, without any information, only a Close button. The pet was not installed.
I attempted to install as root, but the same blank tazpet dialogue without the package being installed.
I attempted to install an inxi pet. When attempting to install as tux, a message about some packages requiring root access, I clicked Install and a blank tazpet Puppy Package Action dialogue window was displayed, without any information, only a Close button. The pet was not installed.
I attempted to install as root, but the same blank tazpet dialogue without the package being installed.
I tested version 15 -- frugal install went well - booted fast
Observations : Opening log-in window doesn't support tab key.
Instead I had to press ENTER to move to next field.
_________________________________
Request ptmtimer 2.5 be included.
http://murga-linux.com/puppy/viewtopic.php?t=112410
_______________________________
Observations : Opening log-in window doesn't support tab key.
Instead I had to press ENTER to move to next field.
_________________________________
Request ptmtimer 2.5 be included.
http://murga-linux.com/puppy/viewtopic.php?t=112410
_______________________________
Result of running from terminal:
Code: Select all
sh-4.4$ cd /mnt/home
sh-4.4$ pwd
/mnt/home
sh-4.4$ tazpet inxi-2.3.8-noarch_all.pet
tar: invalid magic
tar: short read
sh-4.4$ tazpet /mnt/home/inxi-2.3.8-noarch_all.pet
tar: invalid magic
tar: short read
sh-4.4$
I converted the pet to a tazpkg, which appeared to install correctly, however when I attempted run from terminal I got not found. TazPanel has it as Installed package, however it says 0 installed files. Doing a search finds the /var/lib entries and the script that is installed in another puppy, but not in this tazpuppy. Not sure what is happening here.
Edit: I uninstalled the converted tazpkg and installed slitaz inxi package which also installed some dependencies. So it appears that installing the converted pet/tazpkg did not do any dependcy checking.
screenshot below is after attempting to install converted package:
Edit: I uninstalled the converted tazpkg and installed slitaz inxi package which also installed some dependencies. So it appears that installing the converted pet/tazpkg did not do any dependcy checking.
screenshot below is after attempting to install converted package:
- Attachments
-
- Screenshot-TazPanel.png
- (83.01 KiB) Downloaded 689 times
@don570 thats the problem of slim login manager. It cant support tabdon570 wrote:I tested version 15 -- frugal install went well - booted fast
Observations : Opening log-in window doesn't support tab key.
Instead I had to press ENTER to move to next field.
_________________________________
Request ptmtimer 2.5 be included.
http://murga-linux.com/puppy/viewtopic.php?t=112410
_______________________________
@Terry H can you please gave me the download link of that pet package?
uextract does a good job of extracting packages
http://murga-linux.com/puppy/viewtopic.php?t=87864
___________________________________________
http://murga-linux.com/puppy/viewtopic.php?t=87864
___________________________________________
I found that ptmtimer will work if mpg321 or mpg123 is installed
I compiled mpg321 using devx file in first post.
I compiled mpg321 using devx file in first post.
- Attachments
-
- mpg321-tazpup.tar.gz
- Used by ptmtimer
- (33.06 KiB) Downloaded 90 times
Last edited by don570 on Tue 15 Jan 2019, 18:54, edited 1 time in total.
I installed devx and tried to compile mpg123 from sourceforge
https://sourceforge.net/projects/mpg123 ... t/download
However I got this error
The compile of mpg321 went smoothly with only
./configuration --prefix=/usr
_____________________________________________________
Also I have a suggestion...
There needs to be a right click menu for SFS files.
'Load_SFS' is used by some puppy distros.
It is useful for the devx sfs.
_______________________________________
https://sourceforge.net/projects/mpg123 ... t/download
However I got this error
Code: Select all
/bin/grep: /usr/lib/libstdc++.la: No such file or directory
sed: /usr/lib/libstdc++.la: No such file or directory
libtool: error: '/usr/lib/libstdc++.la' is not a valid libtool archive
make: *** [src/libout123/modules/output_esd.la] Error 1
The compile of mpg321 went smoothly with only
./configuration --prefix=/usr
_____________________________________________________
Also I have a suggestion...
There needs to be a right click menu for SFS files.
'Load_SFS' is used by some puppy distros.
It is useful for the devx sfs.
_______________________________________
Also I noticed a strange problem with gtkdialog...
The launching from a button didn't work.
Try this example in tazpup. I couldn't get it to launch DIALOG.
________________________________________________
The launching from a button didn't work.
Try this example in tazpup. I couldn't get it to launch DIALOG.
Code: Select all
#!/bin/sh
#
# Some action function types are still missing.
# See execute_action() for more information.
#
GTKDIALOG=gtkdialog
DIALOG='
<window>
<vbox>
<text>
<label>This is another dialog window.</label>
</text>
<button>
<label>Close</label>
<action function="closewindow">DIALOG</action>
</button>
</vbox>
<variable>DIALOG</variable>
</window>
'
export DIALOG
MAIN_DIALOG='
<window>
<vbox>
<frame Widgets>
<checkbox>
<label>This is a checkbox</label>
<variable>CHECKBOX</variable>
</checkbox>
<entry>
<input>date</input>
<variable>ENTRY</variable>
</entry>
</frame>
<frame Button actions>
<hbox>
<button>
<label>exit</label>
<action>echo You pressed the exit button</action>
<action function="exit">Exit by button</action>
</button>
</hbox>
<hbox>
<button>
<label>launch</label>
<action function="launch">DIALOG</action>
</button>
<button>
<label>closewindow</label>
<action function="closewindow">DIALOG</action>
</button>
</hbox>
<hbox>
<button>
<label>enable</label>
<action function="enable">ENTRY</action>
<action function="enable">CHECKBOX</action>
</button>
<button>
<label>disable</label>
<action function="disable">ENTRY</action>
<action function="disable">CHECKBOX</action>
</button>
</hbox>
<hbox>
<button>
<label>refresh</label>
<action function="refresh">ENTRY</action>
</button>
<button>
<label>clear</label>
<action function="clear">ENTRY</action>
</button>
<button>
<label>fileselect</label>
<action function="fileselect">ENTRY</action>
</button>
</hbox>
</frame>
<hbox>
<button ok></button>
<button cancel></button>
</hbox>
</vbox>
</window>
'
export MAIN_DIALOG
case $1 in
-d | --dump) echo "$DIALOG" "$MAIN_DIALOG" ;;
*) $GTKDIALOG --program=MAIN_DIALOG ;;
esac