[Slackbuilds-users] Slackbuild cloning source from git

[Jeremy Hansen]

Ugh, the Gmail app is making it impossible to reply inline, so it's going
above.

Programs that use subprojects will still need to be manually downloaded and
moved into place. You can see an example of this (with a lot of subprojects
-- 38 if I counted correctly) with my redeclipse SlackBuild.

Due to the massive number of submodules, I listed them all in a separate
file, which helps with both maintenance and building of the package.

https://slackbuilds.org/repository/14.2/games/redeclipse/

My glPortal SlackBuild has far fewer submodules with only 4, so I handle
those individually within the SlackBuild

https://slackbuilds.org/slackbuilds/14.2/games/glPortal/

Hopefully these examples will help.

Jeremy

On Fri, Feb 11, 2022, 11:40 AM Ralph Spitzner <rasp at spitzner.org> wrote:

> Hi all,
> would a Slackbuild cloning the source of the project from github stand any
> chance of
> being accepted (couldn't find any info on this)
> The project in turn uses 'subprojects' which get cloned from git
> recursively.
> There's no tar.gz containing everything and installing the subprojects
> wouldn't make any sense
> as they are only needed to build this and don't install anything
> themselves....
>
>
> regards
>      -rasp
> --
> "ich brauche keine Verschluesselung, mich versteht eh keiner"  -Icke
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220211/2a9674e9/attachment.htm>