TazPuppy 5.0 rc2
-
- Posts: 721
- Joined: Sat 31 Mar 2018, 08:01
- Location: Rakaia
- Contact:
Thanks mistfire ! Great. The package manager works well now.mistfire wrote:TazPup alpha 10 released
After all, I think, it turned out to be a very simple fix by only changing to #!/bin/ash in the /usr/libexec/tazpkg/install script, is that correct ?
(I thought I tested that, and didn't work then, but need to say that I changed all scripts to /bin/ash at that time).
Fred
Now the TazPup alpha 10 is now working nicely. I wonder if tazpup builder cloud script works. If the builder works it can now easily catch up on slitaz rolling releases.
More test to come:
* Perodic Save Session (if it was booted from usb or flash memory)
* Multisession mode
* NVMe boot (Optional, if possible)
If everything works fine. We can declare beta and make formal announcement for this breakthrough
More test to come:
* Perodic Save Session (if it was booted from usb or flash memory)
* Multisession mode
* NVMe boot (Optional, if possible)
If everything works fine. We can declare beta and make formal announcement for this breakthrough
-
- Posts: 721
- Joined: Sat 31 Mar 2018, 08:01
- Location: Rakaia
- Contact:
Nice @darry19662018
Right now I trying to develop a tazpup builder which most binary files are rely from slitaz repo. Only puppy part was busybox and scripts in response to rolling release nature of Slitaz.
On beta release, the version number of tazpup will be aligned to the version number of slitaz to avoid confusion.
Right now I trying to develop a tazpup builder which most binary files are rely from slitaz repo. Only puppy part was busybox and scripts in response to rolling release nature of Slitaz.
On beta release, the version number of tazpup will be aligned to the version number of slitaz to avoid confusion.
-
- Posts: 721
- Joined: Sat 31 Mar 2018, 08:01
- Location: Rakaia
- Contact:
Made in XXXX
pFeee, it looks like when you buy products elsewhere and just stick a label on it 'Made in XXX'
Slitaz is not my OS, even launched by a Puppy. If it was, i will run Slitaz.
Slitaz is not my OS, even launched by a Puppy. If it was, i will run Slitaz.
Re: Made in XXXX
This is as much about 'computing' as about any one distribution Doudou. It's about Puppy because TazPup is a true Puppy/Slitaz blend (though maybe not much from your customer-user point of view). Slitaz pristine has certain weaknesses, as does Puppy - this hybrid is an interesting result that solves some of these issues.hamoudoudou wrote:pFeee, it looks like when you buy products elsewhere and just stick a label on it 'Made in XXX'
Slitaz is not my OS, even launched by a Puppy. If it was, i will run Slitaz.
wiak
What is the command (like dir2pet) to make a tazpkg from a directory?? I've searched but been unable to find.....
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
I don't now what Slitaz could be useful to Puppy..
When i was young, i bought CDs DVDs with main LINUX OS, big or tiny.. When i launched PUPPY, i said 'That is the one'..
I don't know what Slitaz could be useful to Puppy..
Of course i tried Tazpup, and it improves a lot Slitaz.. Pupsave as the main effect.. But all your efforts will now be to get Tazpup as efficient as a true Puppy. But not better, that is impossible. The weak point of Puppy is PPM and dependancies. Slitaz won't help in this matter.
PS / Slitaz is Light because barebone. Just make featured as a Puppy, and Slitaz is bigger than Puppy.. That was said somewhere..
Now, i know that devs don't know what to develop, and they are frightened by new technologies. But here is the way.
I don't know what Slitaz could be useful to Puppy..
Of course i tried Tazpup, and it improves a lot Slitaz.. Pupsave as the main effect.. But all your efforts will now be to get Tazpup as efficient as a true Puppy. But not better, that is impossible. The weak point of Puppy is PPM and dependancies. Slitaz won't help in this matter.
PS / Slitaz is Light because barebone. Just make featured as a Puppy, and Slitaz is bigger than Puppy.. That was said somewhere..
Now, i know that devs don't know what to develop, and they are frightened by new technologies. But here is the way.
The method I have been using is to CD into folder then
For instance if package is named compression.sh-1.8.tazpkg ,
I name the folder compression.sh-1.8
CD out of folder
and the package can be seen if pcmanfm is refreshed.
...But the receipt file might be important because of name of package????
Open up my compression package and see how I wrote the receipt file.
__________________________________________________
Right click utility to compress a folder
compression.sh-1.8.tazpkg
Size 5k
https://drive.google.com/open?id=1QqUSz ... OKqMFmrwrl
Code: Select all
tazpkg pack <folder name>
I name the folder compression.sh-1.8
CD out of folder
Code: Select all
cd ..
...But the receipt file might be important because of name of package????
Open up my compression package and see how I wrote the receipt file.
__________________________________________________
Right click utility to compress a folder
compression.sh-1.8.tazpkg
Size 5k
https://drive.google.com/open?id=1QqUSz ... OKqMFmrwrl
Last edited by don570 on Sat 02 Jun 2018, 18:07, edited 1 time in total.
peebee wrote:What is the command (like dir2pet) to make a tazpkg from a directory?? I've searched but been unable to find.....
http://hg.slitaz.org/tazpkg/raw-file/ti ... kg.es.htmlpack
Create a package from a directory prepared in advance or from an unpacked package. It can also manually create a .tazpkg package (see the [url=file:///storage/emulated/0/cookutils/cookutils.en.html]Cookutils[/url] documentation for the automatic creation of packages).Code: Select all
# tazpkg pack package-version
Open up a tazpackage with uextract and see the receipt file
http://murga-linux.com/puppy/viewtopic. ... 447#992447
________________________________________________
http://murga-linux.com/puppy/viewtopic. ... 447#992447
________________________________________________
You have to create this "receipt file" (equivalent of petspec?) by hand???don570 wrote:...But the receipt file might be important because of name of package????
Open up my compression package and see how I wrote the receipt file.
dir2pet creates petspec for you....
is there a utility to create the "receipt file"??
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
You can use dir2pet and convert instead if you like:peebee wrote:You have to create this "receipt file" (equivalent of petspec?) by hand???don570 wrote:...But the receipt file might be important because of name of package????
Open up my compression package and see how I wrote the receipt file.
dir2pet creates petspec for you....
is there a utility to create the "receipt file"??
http://hg.slitaz.org/tazpkg/raw-file/ti ... kg.es.html
convert
Convierte los paquetes en paquetes SliTaz (.tazpkg) (convert o -c).
Supported packages formats:
paquetes Debian (*.deb, *.udeb)
paquetes RPM (*.rpm)
paquetes Slax (*.sb)
paquetes Puppy (*.sfs, *.pet)
paquetes Slackware (*.tgz)
paquetes NuTyX (*.cards.tar.xz)
paquetes Arch Linux / Alpine Linux (*.apk, *.pkg.tar.gz, *.pkg.tar.xz)
paquetes OpenWrt (*.ipk, *.opk)
paquetes 0Linux (*.spack)
paquetes paldo (*.tar.bz2)
paquetes Void (*.xbps)
paquetes Tinycore (*.tce, *.tcel, *.tcem, *.tcz)Code: Select all
# tazpkg convert alien-paquete
Perhaps this info may be in the thread already but I could not find it -
How to turn off tap to click:
- Open a Sakura terminal (applications, utility, Sakura)
- Type the following command:
synclient
- The contents of the synclient config file will be displayed.
- Type the following command:
synclient TapButton1=0
For further info re how to make this change automatically during boot up see this thread:
http://forum.slitaz.org/topic/synaptics ... ouse-click
Personally I would prefer to learn how to do it the same way I do in puppy: eg: locate the config file, open it in text editor, change the required field and save file, restart flsynclient. But how in slitaz? (flsynclient does not exist)
How to turn off tap to click:
- Open a Sakura terminal (applications, utility, Sakura)
- Type the following command:
synclient
- The contents of the synclient config file will be displayed.
- Type the following command:
synclient TapButton1=0
For further info re how to make this change automatically during boot up see this thread:
http://forum.slitaz.org/topic/synaptics ... ouse-click
Personally I would prefer to learn how to do it the same way I do in puppy: eg: locate the config file, open it in text editor, change the required field and save file, restart flsynclient. But how in slitaz? (flsynclient does not exist)
Odd error here running alpha 10, running Save-Manager / Puppy Event Manager > Save Session, to change the Save Interval to 0,+0, -0 to ask for save at shutdown. When I click 'OK' or 'Enter' key to confirm change, it changes the Save Interval to '5', so it is not possible to set save at shutdown via application.
I believe I have changed it to +0 in some earlier versions, I hadn't attempted to change from default in the last few versions.
I believe I have changed it to +0 in some earlier versions, I hadn't attempted to change from default in the last few versions.
At approximately 18 :30 following doing a new frugal install of alpha 10 I updated the system using tazpkg, the timestamp in /var/log/slitaz/tazpkg.log is more than 1 day in advance of the actual time of the update shown below. The system date and time is set correctly. I am using a save folder carried over from last 3 alphas.
Code: Select all
Extract from /var/log/slitaz/tazpkg.log:
2018-06-03 19:53:27 - Installed - linux (3.16.55) - 896f780b00eaa8c7d8ac8f0c1b6271ac
2018-06-03 19:53:32 - Installed - linux-agp (3.16.55) - b33567abb9217260d1a13c7837a62f75
2018-06-03 19:53:38 - Installed - linux-crypto (3.16.55) - 3c4427ecf9b8483fcc5718e3f43a0718
2018-06-03 19:53:46 - Installe - linux-drm (3.16.55) - a2f11ec86e38bf2ecb8a27f7e73a5783
2018-06-03 19:53:50 d- Installed - linux-firmware (3.16.55) - cca0c98a6e199dc04578f26da14a2a47
2018-06-03 19:53:55 - Installed - linux-hfsus (3.16.55) - 89f655933a87612009a1f7dea2581014
2018-06-03 19:54:01 - Installed - linux-input-touchscreen (3.16.55) - 71578855fb9916e536c843dbbb7303d3slitazisslitazis
2018-06-03 19:54:13 - Installed - linux-sound (3.16.55) - f4c16ee618a14dec2d29001a0353855d
2018-06-03 19:54:21 - Installed - linux-wireless (3.16.55) - 41c8111cd337d490670fc8cb4c348627
2018-06-03 19:54:23 - Installed - syslinux (4.06) - 620329174a1b77fd55265f80b6f19171
2018-06-03 19:54:25 - Installed - syslinux-extra (4.06) - 4940bcaf783bc0d026d1b78ddb1e0bbf
2018-06-03 19:54:27 - Installed - tazlito (507) - 974cb81863b8d18101d535459000e1c3