New package manager

[wysiwyg]

I have recently updated the package manager used in a forked distro of TC and wanted to add it to the repo for TC since it has many more features than the tce-* equivalents.  Reading through the instructions here:

https://forum.tinycorelinux.net/index.php/topic,2072.msg11002.html#msg11002

says that one of the final steps in the use the bcrypt binary to encode it so that the attachments go through to the gmail address listed in that document.  Unfortunately it does not appear that bcrypt is in the Debian repo any longer.  Is there some other encryption to use?  Or should this step just be ignored?

Thanks!

[Rich]

Hi wysiwyg
Why can't you bcrypt the tar file using Tinycore?

[wysiwyg]

Hey Rich, thanks for the reply.  I don't even see bcrypt in the repo there either.

[Rich]

Hi wysiwyg
It's part of the base system:

Code: [Select]

tc@E310:~$ ls -l /usr/bin/bcrypt
-rwxr-xr-x 1 root root 14836 Jun  9  2019 /usr/bin/bcrypt

[wysiwyg]

Oh so it is!!!  Thanks for the tip.  I couldn't find it anywhere lol

[wysiwyg]

For anyone interested, the package manager is called 'pax'.  It should be in the repo as soon as it's processed.

[s1ckn3s5]

Which is the forked distro? I'm just curious =_)
tnx

[wysiwyg]

Hey s1ckn3s5!

The distro is called XiniX.  It was originally forked back in 2017:

https://forum.tinycorelinux.net/index.php/topic,19366.0.html

It is very dated at this point and would be considered a security nightmare due to the outdated software.  I'm in the process of slowly reviving it to the current version of TC, but being a one man show with various projects makes it a slow process.  I'm going to be porting several of the projects used with it over to TC as they are being updated over the coming months.

If you or anyone else has any questions about it, it would be best to DM me.  This is a forum for TinyCore after all

[wysiwyg]

I've been notified that the package is now live for the x86 and x86_64 variants of TC.  Still waiting on inclusion for the Pi's.

Please provide any feedback for the project - especially any bugs.  None are currently known, but if any are found, I can fix them.

[wysiwyg]

One final note.  Currently there is no GUI for this package, so any usage will have to be done from the command line only.  It is discouraged to use the default tce-* scripts and this package manager interchangeably as certain cache files will not get placed when using the tce-* scripts.  This can be resolved by calling 'pax -z' beforehand, but it is an extra step that most will forget.  If you want to make pax your default manager, run 'pax --install' and it will walk you through the process.

I'm working on the man page for this project now and will include it in the next release.  Running 'pax --help' should provide you enough information to successfully use the software though.  DM me with any questions you may have.

[wysiwyg]

Just an FYI to the TinyCore web team, it appears that the Repo Browser is offline.  I get a 404 error when attempting to access it.

Would the team be interested in a server-side that is similar to Debian's?  This way package managers could actually search through the packages.  I know there is the ability in the native tce GUI, but it is rudimentary and not a search based on keywords or words in descriptions (nor for files).

[Rich]

Hi wysiwyg
I just checked. Repo appears to be up.

[CNK]

Would the team be interested in a server-side that is similar to Debian's?  This way package managers could actually search through the packages.  I know there is the ability in the native tce GUI, but it is rudimentary and not a search based on keywords or words in descriptions (nor for files).

The "Provides" search in the terminal tce-ab package manager allows searching for keywords and files. Or run "provides.sh" to search for files.

I find tce-ab already works as well as Debian package managers work for me. The only feature I miss is the provision for Debian packages to have optional dependencies. On TC I have to manually edit .dep files (which isn't well accomodated by TC's extension updater scripts, but at least that's easier than it is with Debian).

[wysiwyg]

How does it acquire the data to search?  I would presume it downloads all the .info files for all the packages...  Without a server-side search script of some type, it's eating up bandwidth.

The package manager I just uploaded to the repo can list optional dependencies in the package .dep files (using the format [optional.tcz|installed.tcz]).  There's a switch to install them as well.  I know this won't help you, but it was something I thought about and incorporated.  There's also the ability to install certain files out of a package instead of the entire contents.

[Rich]

Hi wysiwyg

How does it acquire the data to search? ...

There are some files with information:

Code: [Select]

dep.db.gz Lists each extension followed by its direct dependencies.
info.lst Lists which extensions are available in the repo.
md5.db.gz Lists md5sum for each extension.
provides.db Lists which files each extension provides including their paths.
sizelist Lists how big each extension is.
tags.db.gz Lists which tags show up in each extensions .info file.
Some of these files are also available in a compressed format.
Here's a list:

Code: [Select]

     36592 Jan 28 10:21 dep.db.gz
     56002 Jan 28 10:21 info.lst
     14221 Jan 28 10:21 info.lst.gz
     89232 Jan 28 10:21 md5.db.gz
  33378319 Jan 28 10:21 provides.db
   3249743 Jan 28 10:21 provides.db.gz
    179537 Jan 28 10:21 provides.db.zsync
     79429 Jan 28 10:21 sizelist
     23267 Jan 28 10:21 sizelist.gz
     36370 Jan 28 10:21 tags.db.gz