From woquendo at gmail.com Fri Jul 3 20:10:19 2026 From: woquendo at gmail.com (William Oquendo) Date: Fri, 3 Jul 2026 15:10:19 -0500 Subject: [sbopkg-users] Specify version from command line and and read source from current dir? Message-ID: Hi, First thanks for sbopkg. Sometimes, I want to use/test the current slackbuild but with a newer package version. For instance, for apptainer, and the current sbopkg configuration (I am using /var/lib/sbopkg/SBo-git/), the apptainer version is too old, it is 1.1.6. I want to test with the current one, 1.5.2. The ideal use would be to download the current source at my current directory, wget -c https://github.com/apptainer/apptainer/releases/download/v1.5.2/apptainer-1.5.2.tar.gz and specify the version as a flag VERSION=1.5.2 sbopkg -i apptainer But of course that does not work, even the version flag is kept on the old value 1.1.6. Actually, the slackbuild has something like VERSION=${VERSION:-1.6.1} and the .info also has the version written and maybe it is overwriting everything. I currently do something which is an ugly workaround: enter the dir /var/lib/sbopkg/SBo-git/system/apptainer, put there the soruce and run there the slackbuild script directly with the VERSION env flag. Reading the slackbuild it seems that it uses CWD=$pwd for the source, so it wont work either to find the source in another directory. But that can be mitigated by putting the source in the cache. The problem is with the env var. Of course apptainer is just an example, I know that is a big version jump and so on, and the general goal of this post is to know if there is a way to easy the handling of different versions and sources besides modifying the repo. Many thanks -- Best regards / Cordialmente, William-Fernando Oquendo -------------------------- Este correo puede carecer de tildes o e?es debido al teclado. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Jul 4 13:54:01 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 4 Jul 2026 20:54:01 +0700 Subject: [sbopkg-users] Specify version from command line and and read source from current dir? In-Reply-To: References: Message-ID: <20260704205401.538c9f8f@home.slackie.org> >Hi, >First thanks for sbopkg. >Sometimes, I want to use/test the current slackbuild but with a newer >package version. For instance, for apptainer, and the current sbopkg >configuration (I am using /var/lib/sbopkg/SBo-git/), the apptainer version >is too old, it is 1.1.6. I want to test with the current one, 1.5.2. > >The ideal use would be to download the current source at my current >directory, >wget -c >https://github.com/apptainer/apptainer/releases/download/v1.5.2/apptainer-1.5.2.tar.gz >and specify the version as a flag >VERSION=1.5.2 sbopkg -i apptainer >But of course that does not work, even the version flag is kept on the old >value 1.1.6. Actually, the slackbuild has something like >VERSION=${VERSION:-1.6.1} >and the .info also has the version written and maybe it is overwriting >everything. > >I currently do something which is an ugly workaround: enter the dir >/var/lib/sbopkg/SBo-git/system/apptainer, put there the soruce and run >there the slackbuild script directly with the VERSION env flag. > >Reading the slackbuild it seems that it uses CWD=$pwd for the source, so it >wont work either to find the source in another directory. But that can be >mitigated by putting the source in the cache. The problem is with the env >var. > >Of course apptainer is just an example, I know that is a big version jump >and so on, and the general goal of this post is to know if there is a way >to easy the handling of different versions and sources besides modifying >the repo. Hi sbopkg is designed to run originally to run the script from the repo, so local edit is not possible, but later on, we have added a local edit features, which is not available in CLI mode. You need to run it on TUI mode by running sbopkg as root without any option. Select Search > Custom. You can edit .info or .SlackBuild locally there -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 870 bytes Desc: OpenPGP digital signature URL: From woquendo at gmail.com Tue Jul 7 14:12:22 2026 From: woquendo at gmail.com (William Oquendo) Date: Tue, 7 Jul 2026 09:12:22 -0500 Subject: [sbopkg-users] Specify version from command line and and read source from current dir? In-Reply-To: <20260704205401.538c9f8f@home.slackie.org> References: <20260704205401.538c9f8f@home.slackie.org> Message-ID: Hi, understood. Thanks. On Sat, Jul 4, 2026 at 8:54?AM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > >Hi, > >First thanks for sbopkg. > >Sometimes, I want to use/test the current slackbuild but with a newer > >package version. For instance, for apptainer, and the current sbopkg > >configuration (I am using /var/lib/sbopkg/SBo-git/), the apptainer version > >is too old, it is 1.1.6. I want to test with the current one, 1.5.2. > > > >The ideal use would be to download the current source at my current > >directory, > >wget -c > > > https://github.com/apptainer/apptainer/releases/download/v1.5.2/apptainer-1.5.2.tar.gz > >and specify the version as a flag > >VERSION=1.5.2 sbopkg -i apptainer > >But of course that does not work, even the version flag is kept on the old > >value 1.1.6. Actually, the slackbuild has something like > >VERSION=${VERSION:-1.6.1} > >and the .info also has the version written and maybe it is overwriting > >everything. > > > >I currently do something which is an ugly workaround: enter the dir > >/var/lib/sbopkg/SBo-git/system/apptainer, put there the soruce and run > >there the slackbuild script directly with the VERSION env flag. > > > >Reading the slackbuild it seems that it uses CWD=$pwd for the source, so > it > >wont work either to find the source in another directory. But that can be > >mitigated by putting the source in the cache. The problem is with the env > >var. > > > >Of course apptainer is just an example, I know that is a big version jump > >and so on, and the general goal of this post is to know if there is a way > >to easy the handling of different versions and sources besides modifying > >the repo. > > > Hi > > sbopkg is designed to run originally to run the script from the repo, so > local > edit is not possible, but later on, we have added a local edit features, > which > is not available in CLI mode. You need to run it on TUI mode by running > sbopkg > as root without any option. > > Select Search > Custom. You can edit .info or .SlackBuild locally there > > > > -- > Willy Sudiarto Raharjo > _______________________________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > https://sbopkg.org/mailman/listinfo/sbopkg-users > -- Best regards / Cordialmente, William-Fernando Oquendo -------------------------- Este correo puede carecer de tildes o e?es debido al teclado. -------------- next part -------------- An HTML attachment was scrubbed... URL: