Look at the following: lws root # ACCEPT_KEYWORDS='~x86' emerge -pv subversion
These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] net-www/apache-2.0.48-r4 +berkdb +gdbm -ldap [blocks B ] =sys-devel/autoconf-2.58* (from pkg dev-util/subversion-0.37.0) [ebuild N ] net-misc/neon-0.24.4 +ssl +zlib -expat [ebuild N ] dev-util/subversion-0.37.0 +ssl +apache2 +berkdb +python -emacs Note that autoconf blocks neon. If we unmerge autoconf (lots fo stuff breaks...) including our ability to build apache. Of course I can always build apache then unmerge autoconf, then build neon and subversions, then reemerge autoconf? (maybe), it seems twisted. Any comments? -- [EMAIL PROTECTED] mailing list
