I was trying to use slackyd package manager in Salix (even though gslapt is excellent) but could not use it because slackyd looks for the file FILELIST.TXT, which is not found in its repository: http://download.salixos.org/i486/14.1/
This file is present in other Slackware repositories, for example:
http://www.studioware.org/files/package ... ware-14.1/
http://packages.slackonly.com/pub/packages/14.1-x86/
http://repository.slacky.eu/slackware-14.1/
Why this difference and where can the file FILELIST.TXT be found for Salix repository? Thanks.
Why salix repository does not have FILELIST.TXT ?
Re: Why salix repository does not have FILELIST.TXT ?
There is no such file, because it is not needed by slapt-get.
Re: Why salix repository does not have FILELIST.TXT ?
Can it be included if it does not take too much resources? Because otherwise Salix repository is tending to become different from other Slackware repositories.
Re: Why salix repository does not have FILELIST.TXT ?
It can be included, but it won't be included, because it is not needed and I'd rather not wait for a few minutes to create it every time I update the repos.
If you really want it so much, feel free to mirror the repository using rsync and create it locally. But by using slackyd, or any other package manager we do not support, you're on your own.
If you really want it so much, feel free to mirror the repository using rsync and create it locally. But by using slackyd, or any other package manager we do not support, you're on your own.
Re: Why salix repository does not have FILELIST.TXT ?
It is not only the FILELIST.TXT file. It is created at once. To use salix repo with slackyd the checksums package has also to be created including md5 for every package and not only txz. Which takes too much time even when a single package added or upgraded in repos. to not mention MANIFEST.bz2 which also need too much time. Both need more than 20 minutes + 20 minutes for i486 repo.
I have done this in slackel repos adding new code inside metagen.sh script.
So i will continue to do it. I do not like slackyd. Slapt-get/gslapt is very good tool and easy to use. No need for other tool.
So i agree with gapan.
Also, Salix repos are not tend to be different from other slackware repos. The programs used to upgrade are different.
I have done this in slackel repos adding new code inside metagen.sh script.
So i will continue to do it. I do not like slackyd. Slapt-get/gslapt is very good tool and easy to use. No need for other tool.
So i agree with gapan.
Also, Salix repos are not tend to be different from other slackware repos. The programs used to upgrade are different.