(Ccing the ifolder-developers)
> On Mon, 2010-05-17 at 21:53 -0400, CSights wrote:
> > Hi directhex,
> >
> > I'm experimenting with simias, trying to get both client and server to
> >
> > install in the same file system. In the process I discovered
> > SimiasClient.dll was different depending on whether --run-asclient was a
> > compile flag or not. mono-api-check reports the two versions are the
> > same and the size is the same. But the value of "webdir" is different...
> > it is passed in via the toplevel configure.in .
> >
> > So I decided to not use simias-common for now and just divide up the
> > files
> >
> > between simias-client and simias-server. (but keeping libsimias*)
> >
> > The experiment appears to have worked. I can install simias-client
> > and
> >
> > simias-server on the same computer. Then install ifolder GUI and
> > synchronize folders between client/server on the same computer.
> >
> > The problem is that simias-client now depends on simias-server. :( I
> >
> > wanted to install both , but not HAVE to install both. :)
> >
> > To me it seems that clideps is not looking in the SAME package to
> > resolve
> >
> > dependencies. I.e. it is first looking in simias-server instead of
> > simias- client and finds what it thinks is a solution in simias-server.
> > Instead it should first check simias-client, say "oh, simias-client
> > 1.DLL depends on simias-client 2.DLL, do nothing".
> >
> > Any hints? Any quick way to override the addition of simias-server to
> >
> > simias-client dependencies?
> >
> > I think I know that the CLI Provides comes from DEBIAN/clideps. This is
> >
> > generated by dh_makeclilibs. Then dh_clideps checks the DLLs and decides
> > what packages to depend upon based on the DEBIAN/clideps. So dh_clideps
> > is probably where the problem lies.
> >
> > If you're interested, the debian directory is at:
> > lp:~csights/+junk/simias-svn+exp. I'm using an svn trunk from
> > 2010-05-11. I couldn't figure out the get-orig-source for svn, so I
> > just manually downloaded the tarball. I've posted it for you here:
> > http://dl.dropbox.com/u/3224703/simias_trunk20100511.orig.tar.gz
>
> My Perl is a little rusty, but it looks like the issue is
> in /usr/bin/dh_clideps at around line 500 - $clilibdata{"$name/$key"} is
> gonna contain more than one match for the same name/key combo due to
> SimiasClient having the same name/key in both situations, which is a
> situation I don't think we ever expected to deal with.
>
> Here are some possible solutions:
> * Fix dh_clideps somehow to handle multiple duplicates in different
> packages
> * Fix Simias to rename (or use a different key) the library depending on
> whether it's client or server mode
>
> I'm not sure which is the easier route. Clearly dh_clideps is at fault
> for not handling this scenario - but the scenario should never happen,
> because you should never have the same name/key for a library with
> different contents.
>
> Thoughts?
I like the idea of using a different key depending on if the library is
different when the source is compiled in server versus client mode. This way
we will also be able to see what should go in simias-common or not.
How are keys generated? (Does it have anything to do with the
iFolder.snk
files?) If that can be changed in the Makefiles it should be possible to
search for "asclient" conditionals in the Makefiles and also change what key
is being stuck on the dll.
The second best option is to modify dh_clideps. Maybe an explicit
check
on the current package's clideps would be enough?
The ickiest option IMO would be to rename the dlls. Too many changes.
I've CCed the ifolder devel list to see if they have any opinion.
TTYL,
Chad.
------------------------------------------------------------------------------
_______________________________________________
ifolder-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ifolder-devel
