[SOLVED] What is the recommended way to build a Slackware package for software that does not provide a source code tarball?
by FlinchX from LinuxQuestions.org on (#592WB)
I looked at the reference SBo templates at https://slackbuilds.org/templates/ and they seem to assume that there's a source code tarball for the package that is being built.
That is not always the case. Sometimes there's just a source code repository without tags/releases.
What is the recommended way to write the SlackBuild for those? I'd like to learn the conventions that buildscript writers follow because I can imagine at least two different ways of doing it:
1. Clone the repository and work with it directly
2. Have the SlackBuild produce a snapshot source code tarball (for git, it would be `git archive`, but other version control systems have similar functionality), then process that tarball the same way like a regular source code tarball.
That is not always the case. Sometimes there's just a source code repository without tags/releases.
What is the recommended way to write the SlackBuild for those? I'd like to learn the conventions that buildscript writers follow because I can imagine at least two different ways of doing it:
1. Clone the repository and work with it directly
2. Have the SlackBuild produce a snapshot source code tarball (for git, it would be `git archive`, but other version control systems have similar functionality), then process that tarball the same way like a regular source code tarball.