[sbopkg-users] Potential package conflicts when using sbopkg

[JCA]

   I have just started using sbopkg and it really simplifies the chores
associated with building packages with long dependencies lists. There is
something that worries me though:

   Imagine I want to build packages P1 and P2. P1 depends on a number of
other packages, P3 being one of them. Likewise, P3 also is one of the
dependencies for building P2. I have two questions based on this scenario:

   1) When building P1, P3 will be downloaded (if necessary) and installed.
When building P2, P3 will be installed again. Why, given that it is already
installed? This seems to be the default behavior of sbopkg, but it can be
changed with -k, I believe. But, why not make this the default behavior?
This actually leads to my second question.

   2) Is it possible for P1 and P2 to be dependent on different versions of
P3 under the wraps? At first I thought that would not be the case, because
packages explicitly include version information. However, when building
cinelerra for 14.0 the build failed on the grounds that the MD5 checksum
for the a52dec-0.7.4 package in the sbopkg cache was different from that
expected by the cinelerra build scripts. I deleted the tarball associated
with a52dec-0.7.4 from /var/cache/sbopkg, relaunched the cinelerra  build
process, and this time it completed correctly, after sbopkg downloaded and
installed a52dec-0.7.4 anew. However, I do not understand why the checksum
problem arose in the first place, and I also wonder if the new a52dec-0.7.4
package might be incompatible with the package that forced its installation
(I forget which one it was) before installing cinelerra.

   Any help would be much appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20131113/dca85447/attachment-0001.html>