Re: [Slackbuilds-users] Deal with source that requires submodules

2022-07-28 Thread B. Watson
On Fri, 29 Jul 2022, Christoph Willing wrote: Although there's an easy solution in this particular case, I would be interested in hearing of a more general solution for cases where there is no such additional tarball available. I maintain another SlackBuild which has exactly the same

Re: [Slackbuilds-users] Deal with source that requires submodules

2022-07-28 Thread Jeremy Hansen
On Thu, Jul 28, 2022, 4:39 PM Christoph Willing wrote: > On 29/7/22 04:11, Heinz Wiesinger wrote: > > On Thursday, 28 July 2022 20:08:02 CEST Wen-Wei Kao wrote: > >> Hello, > >> > >> Recently while writing SlackBuilds, there is a particular package > (https:// > >> github.com/fcitx/libime) that

Re: [Slackbuilds-users] Deal with source that requires submodules

2022-07-28 Thread Christoph Willing
On 29/7/22 04:11, Heinz Wiesinger wrote: > On Thursday, 28 July 2022 20:08:02 CEST Wen-Wei Kao wrote: >> Hello, >> >> Recently while writing SlackBuilds, there is a particular package (https:// >> github.com/fcitx/libime) that requires a submodule pulled in before >> compiling, but the Github

Re: [Slackbuilds-users] Deal with source that requires submodules

2022-07-28 Thread Heinz Wiesinger
On Thursday, 28 July 2022 20:08:02 CEST Wen-Wei Kao wrote: > Hello, > > Recently while writing SlackBuilds, there is a particular package (https:// > github.com/fcitx/libime) that requires a submodule pulled in before > compiling, but the Github release tags' sources don't have it included. >

[Slackbuilds-users] Deal with source that requires submodules

2022-07-28 Thread Wen-Wei Kao
Hello, Recently while writing SlackBuilds, there is a particular package (https:// github.com/fcitx/libime) that requires a submodule pulled in before compiling, but the Github release tags' sources don't have it included. What are the recommended ways to deal with this? Should I mark both as