VTG should have an ability to be built without afrodite

[GoogleCodeExporter]

What steps will reproduce the problem?
1. ./configure --enable-vtg-plugin --disable-afrodite
2. make

What is the expected output? What do you see instead?
It shouldn't fail with this error:

configure: error: afrodite library was disabled from configure command line, 
but vtg plugin requires it. Please disable vtg plugin too or reenable afrodite.

On some systems (ex. Gentoo) two separate packages are needed: one with 
"--disable-vtg-plugin --enable-afrodite" and another with "--enable-vtg-plugin 
--disable-afrodite" because other packages are using afrodite, too (ex. 
monodevelop-vala).

This should be a warning, not an error.

What version of the product are you using? On what operating system?
I'm using vtg-0.12.0.0-beta2.tar.bz2 on my Gentoo Linux amd64.

Please provide any additional information below.
Another way could be adding an --extenal-afrodite flag or something like that.

Original issue reported on code.google.com by ulltor on 6 May 2011 at 2:39

[GoogleCodeExporter]

Yes this is true but can't you build the two packages within the same 
compilation directory as debian mantainers are doing?

Anyway, I'm looking to fix this too

Original comment by seje...@gmail.com on 9 May 2011 at 11:49

[GoogleCodeExporter]

All packages in Gentoo are built on each user's machine in
/var/tmp/portage/${CATEGORY}/${PACKAGE}-${VERSION}/work/,
and this behaviour is hardcoded into package manager.

So I must use separate dirs:

/var/tmp/portage/dev-libs/afrodite-0.12.0.0_beta2/work/ and
/var/tmp/portage/x11-plugins/vtg-0.12.0.0_beta2/work/.

The actual problem is that before merging the package into
the system, Gentoo installs it into
/var/tmp/portage/${CATEGORY}/${PACKAGE}-${VERSION}/image/
directory, counts and registers all files, and only after this
it moves binaries into real system tree. On the step of registering
vtg's files it finds out that some files (libafrodite.so, etc.) are
already in the system tree and belong to another package. So Gentoo
refuses to install vtg and exits with error.

Original comment by ulltor on 9 May 2011 at 3:01

[GoogleCodeExporter]

This should be fixed now, but I haven't had the time to do a build against a 
system wide installed copy of libafrodite. Can you check if it works for you 
using the current git master or do you need another beta tarball?

Original comment by seje...@gmail.com on 10 May 2011 at 5:56

• Changed state: Started

[GoogleCodeExporter]

I just uploaded a beta 3 because I fixed some more critical bugs.

I'll just close this bug, but feel free to reopen it or file another one if you 
have more issues with the vtg build.

Original comment by seje...@gmail.com on 10 May 2011 at 9:19

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by seje...@gmail.com on 27 Jul 2011 at 11:34

• Changed state: Release0.12.0

[GoogleCodeExporter]

Original comment by seje...@gmail.com on 27 Jul 2011 at 11:36

• Changed state: Released
• Added labels: Milestone-Release0.12.0