[SOLVED] Sbosrcarch and third party package managers
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As you know third party package manager which have the ability to deal with SBo (sbopkg, sbotools, slpkg) always look at .info files to find the location of source files. I wonder how to use these tools so that they download source files from sbosrcarch instead?
One possible way would be manually editing .info files (I think this will work for sbotools). However, using this method for every single package would be a nightmare. What do you think? do you know a more automated way to do this?
slackrepo automatically tries slackbuildsdirectlinks if the location in the .info file fails for any reason, I'm going to extend this for sbosrcarch in the very near future.
As you know third party package manager which have the ability to deal with SBo (sbopkg, sbotools, slpkg) always look at .info files to find the location of source files. I wonder how to use these tools so that they download source files from sbosrcarch instead?
One possible way would be manually editing .info files (I think this will work for sbotools). However, using this method for every single package would be a nightmare. What do you think? do you know a more automated way to do this?
I'm intending to make sbotools able to check sbosrcarch automatically if a download fails, there's an issue about it on github: https://github.com/pink-mist/sbotools/issues/7
I just haven't had time to code it yet, but I don't think it will be too hard to do.
Anyway, I think it would be necessary feature for source based package manager so that users have the ability to use different repositories same as binary ones. However, I don't know how much work needed as I know nothing about coding.
Thank you very much. I am looking forward to see how it goes for slackrepo and sbotools
Maybe I couldn't clarify my purpose due to my English languages. As far as I understood this command just download source files and store them in a specific location. I didn't mean that. I referred to an option which can give the user the ability to change source based repositories during dealing with SBo packages. For example using sbosrcarch for downloading source of jdk package instead oracle site which has been mentioned in "DOWNLOAD" field of jdk.info.
PS: Why does there is nothing about --download-only in slpkg man page?
PS: Why does there is nothing about --download-only in slpkg man page?
It is in the man page. Under the -s, --sync section.
Code:
--resolve-off : Switch off automatic resolve dependencies.
--download-only : Download packages without install.
--directory-prefix=[path/to/dir/] : Download packages in specific directory.
I've made sbotools try sbosrcarch if the regular download fails or doesn't verify.
If you'd like to try it out you can get a release candidate of the source here: sbotools-1.10RC1.tar.gz
or a ready-made package here: sbotools-1.10RC1-noarch-1_SBo.tgz
There's also some other improvements in there, but they're not too relevant to the issue at hand =)
Please report any issues you find at https://github.com/pink-mist/sbotools/issues or the #sbotools irc channel on freenode.
I've made sbotools try sbosrcarch if the regular download fails or doesn't verify.
If you'd like to try it out you can get a release candidate of the source here: sbotools-1.10RC1.tar.gz
or a ready-made package here: sbotools-1.10RC1-noarch-1_SBo.tgz
There's also some other improvements in there, but they're not too relevant to the issue at hand =)
Please report any issues you find at https://github.com/pink-mist/sbotools/issues or the #sbotools irc channel on freenode.
Thanks suppy, I haven't been faced any problem yet.
I have another suggestion, Is it possible to extend this feature to local source repo too? I mean since sbotools have the ability to keep source files in a dedicated directory, is it possible to give priority to this directory by sboinstall command so that sboinstall first looks for given version of source files in this directory then main source repo and then sbosrcarch? This feature will prevent re-downloading already downloaded source files.
I have another suggestion, Is it possible to extend this feature to local source repo too? I mean since sbotools have the ability to keep source files in a dedicated directory, is it possible to give priority to this directory by sboinstall command so that sboinstall first looks for given version of source files in this directory then main source repo and then sbosrcarch? This feature will prevent re-downloading already downloaded source files.
If you're talking about the /usr/sbo/distfiles directory, then if that has a source file with the right name and md5 it will be used instead of downloading already. So long as you don't sboclean -d at least.
If that wasn't what you meant, please submit a feature request on the issues page =)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.