On 03.04.2012 21:55, Dan Langille wrote:
> A long running problem with the Bacula port is being worked on by Alonso
> Cárdenas Márquez. I have been testing out his changes recently.
>
> The problem: shared libraries installed by one of the ports are
> reinstalled by the other ports.  This problem has raised its head in a few
> recent posts.
>
> The proposed solution at present involves making bacula-client a dependent
> of bacula-server.  Let bacula-client install the shared libraries.
>
> Downside: you can't install bacula-server without first installing
> bacula-client.
>
> Benefit: it solves the problem.
>
> Better solution: create a third port which installs JUST the shared
> libraries.  That solution isn't in scope at present.
>
> Comments?  Questions?  Volunteers for testing?  Volunteers for
> improvements to the solution?

One simple solution would be to create a 'bacula-libs' port, let it 
compile as little as possible and install only the shared libraries. 
'bacula-server' and 'bacula-client' ports wouldn't then install the 
libraries, although they compile them.

Or: modify the install-scripts to check first whether the shared 
libraries exist or not, and then decide whether to install them and mark 
them part of pkg-plist (I'm not really sure the latter is possible though).

Further thoughts? :)

--
Silver

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users