closed not a support question
Ceel
offlineAdministrator
Hi Aleksej,
http://www.slitaz.org/get/ returns Not Found The requested URL /get/ was not found on this server. Good link is http://www.slitaz.org/en/get/
Why no link to
SliTaz Rolling release (weekly) - 03 Jan 2016
at http://www.slitaz.org/en/ (and other languages)?
Have a nice evening.
Genesis
offlineMember
Hi Aleksej!
Your work at Slitaz pages is excellent!
If it isn't asking too much, at "Welcome to SliTaz" section at http://www.slitaz.org, we could add a second line of text:
"SliTaz is a 'rolling release' Linux, updated weekly with new functionalities and corrections."
And at "Quick Download" section:
"Slitaz Weekly (32 and 64 bits) is the latest and recommended version to download."
At http://www.slitaz.org/en/get , I have no more suggestions. The information there is now clear, direct, and simple to understand. ;D
I believe that with these little changes we can improve a lot the Slitaz website.
Have a nice day!
PS: sorry for any English mistakes...
linuxscripts
offlineMember
@Aleksej,
I all ready thought the archiving to a single file was the case cpio was used first.
Thanks for the other info as well (also didn't know fs was cpio'd and lzma'd, whereas receipt, files.list, md5sum, description.txt was then archived together using CPIO into filename.tazpkg
I understand the regular tazpkg thus requires cpio. However, isn't it possible with your tazpkg beta to also provide support for tar besides cpio (so support both) ? That way, packages can then also be made the same way (archiving fs using tar and lzma or gzip, and putting fs together with receipt, files.list, md5sum, description.txt into filename.tazpkg using tar ? I think that would be an improvement, since as mentioned, windows doesn't have good cpio archivers, so making tazpackages on windows is much more difficult; also even on linux, tar is better supported (with regular gui-based compression utilities, not via commmand line)
Aleksej
offlineCoder-hobbyist
Hi linuxscripts,
I understand the regular tazpkg thus requires cpio. However, isn't it possible with your tazpkg beta to also provide support for tar besides cpio (so support both) ?
I have to disappoint you. Tazpkg beta, or Tazpkg test development is discontinued on the third page of this topic. And here the link FYI:
http://forum.slitaz.org/topic/tazpkg-beta-needs-testing/page/3#post-39873
Many thanks to all who participated in the testing!
From now package "tazpkg-test" discontinued, and maybe used in the future to test some extremely updates.
I should like to close this topic for a long time, not to be confuse anyone.
------
TazPkg now is (relatively) stable. Format of packages we using is here for a long years. I not plan to change package format because I see no point in it. We use package format fulfilled SliTaz needs.
I don't get your idea, why you use Windows to develop SliTaz packages.
Even if I'll provide TAR support, even if you learn how to make SliTaz packages, even if you write your own scripts to make your SliTaz packages in the Windows — your packages will be definitely bad. I can tell you why.
I doubt windows' archiving tools supporting Linux file system attributes: files permissions and ownership. Most files should be owned by root; some content of /var/www is owned by user www. Executable files should have rwxr-xr-x (755) permissions, regular files: rw-r--r-- (644), regular folders rwxr-xr-x (755). Some files in /etc is rw------- (600).
When I mount my ntfs partition, all files and folders inside it have permissions rwxrwxrwx (755), this mean: anyone can read, write and execute any file. I doubt it is good.
And now I close the topic: it fulfilled it's mission. Even more.
This topic has been closed to new replies.
