[Slackbuilds-users] sbotools config issues

J. Milgram milgram at cgpp.com
Tue Mar 12 02:28:52 UTC 2024


Thanks Matteo, all very interesting. So I was probably installing 
correct -current SBo's right from the beginning.

I wonder if sbotools looks at /etc/slackware-version to decide which 
repo to default to.

Good advice on going to LQ for questions about -current (and sbotools 
too, I guess.)

thanks again all! As mentioned in other post, everything's installed 
now, and running properly.

r/
Judah

On 3/11/24 07:06, Matteo Bernardini wrote:
> hi,
>
> just for testing I downloaded, packaged and installed sbotools from here
>
> https://slackbuilds.org/repository/15.0/system/sbotools/
>
> following what's written on the documentation
>
> https://pink-mist.github.io/sbotools/documentation/
>
> I run "sbosnap fetch" to download the repository and I saw that in 
> /usr/sbo/repo what is downloaded by default the unofficial repository 
> for current that I maintain (check /usr/sbo/repo/.git/config) that 
> shouldn't be used for 15.0 (maybe some other default should be set in 
> the package on SBo) but should help who's running current.
>
> the reason why it should help who's running current is that it 
> contains patches for the broken scripts that don't build on current 
> and that are reported to me through the dedicated stickied thread on 
> LQ and, also, scripts that are added to current are removed from there 
> to avoid risks of overlap with what is already in current, like Gene 
> explained in another message of this thread.
>
> what I don't edit in my unofficial repository for current are the 
> mentions of the removed scripts in the REQUIRED variables in the 
> *.info files of what use these scripts as dependencies: that would be 
> simply non maintenable because simple version changes of these scripts 
> would result in a gazillion of conflicts in these git forks.
>
> users of current should learn to ignore these non existant scripts 
> warning (and optionally refer to this list to check what has been 
> removed and why https://cgit.ponce.cc/slackbuilds/refs/heads), still 
> like Gene pointed out in the previous message
>
> this to say that the repository you were using as default should 
> already had been probably ok and the "unable to locate" message were 
> normal (I don't think you ever had a repository for 15.0 setup in 
> sbotools).
>
> consider also that this mailing list is not actually the proper place 
> to help you in your eventual issues with current as the developer's 
> version of Slackware is not supported by SBo: if you find problems 
> using this unofficial repository for current or any of the SBo's 
> scripts with current, IMHO, the best option is to open a topic on LQ 
> describing the issue and your setup.
>
> Matteo
>
> _______________________________________________
> 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/
>



More information about the SlackBuilds-users mailing list