WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Missing shared object for svn in new install (current)  (Read 1252 times)

Offline Nathan_SR

  • Jr. Member
  • **
  • Posts: 82
    • Quick-Save-Live
Re: Missing shared object for svn in new install (current)
« Reply #15 on: August 14, 2018, 05:07:04 PM »
Thanks Misalf for pointing it out.

As it says:

Quote
It is easy to leave out a required dependency from your .dep file. Do use base norestore, and check the dependencies in particular.

An automated script/tool would be handy to check and correct it out, which is the subject of my posts here.

Another script/tool by Jason W already checks if the new extension will overwrite any existing libraries. My suggestion is an extension to that script. Hope all these scripts get documented, in that wiki page as well, for the benefit of future extension makers.
« Last Edit: August 14, 2018, 05:10:00 PM by Nathan_SR »

Offline polikuo

  • Sr. Member
  • ****
  • Posts: 353
Re: Missing shared object for svn in new install (current)
« Reply #16 on: August 14, 2018, 08:22:40 PM »
As a means of detecting library dependencies of binaries in all packages ...
I've made a script for that purpose years ago.
The latest script is available on my github.
To run it, type
Code: [Select]
./scriptname /tmp/tcloop/extension_name

Offline Nathan_SR

  • Jr. Member
  • **
  • Posts: 82
    • Quick-Save-Live
Re: Missing shared object for svn in new install (current)
« Reply #17 on: August 14, 2018, 09:57:58 PM »

Yes polikuo, this is exactly, what I was referring to.

@Juanito,

is there a possibility of running the polikuo's script, to detect missing libraries of existing/new extensions, at either end ( i.e. Maintainer's as well as the Central Quality Controller's end )

This will help to prevent issues like that of svn, discussed in this topic.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 10202
Re: Missing shared object for svn in new install (current)
« Reply #18 on: August 15, 2018, 01:45:35 AM »
The svn error was caused by my own typo  :P

Dependencies found in this way are only part of the issue, there are also run time dependencies and "nice to have" dependencies to be considered.