Common interface to slackbuilds resources
by igadoter from LinuxQuestions.org on (#4ZSWB)
Hi folks,
slackbuilds resources are ftp://, http(s):// git:// file:// the problem is to create engine to query resource - say to search for some particular slackbuild. It would be much easier to use the same interface with one of those as backend offering some natural actions. Say I have bash script it resolves dependencies - but at this moment it works only with http(s) if web page provides search engine. Here are people having troubles with sbo scripts on -current. For -current there are only two http(s) resources and both are not of much use due to how search engines work. I don't know much about git - how to use it, for me simplest is to use file:// from archived scripts. But is completely unsatisfactory - it would be much easier to have interface with say plugin to serve particular resource. Someone interested in app to maintain/use/whatever slackbuilds would just rely on this interface. System of data maintain allowing searching and other things. Real action is done via plugin depending on what resource is accessible.
slackbuilds resources are ftp://, http(s):// git:// file:// the problem is to create engine to query resource - say to search for some particular slackbuild. It would be much easier to use the same interface with one of those as backend offering some natural actions. Say I have bash script it resolves dependencies - but at this moment it works only with http(s) if web page provides search engine. Here are people having troubles with sbo scripts on -current. For -current there are only two http(s) resources and both are not of much use due to how search engines work. I don't know much about git - how to use it, for me simplest is to use file:// from archived scripts. But is completely unsatisfactory - it would be much easier to have interface with say plugin to serve particular resource. Someone interested in app to maintain/use/whatever slackbuilds would just rely on this interface. System of data maintain allowing searching and other things. Real action is done via plugin depending on what resource is accessible.