use.local.desc states: dev-vcs/git:subversion - Include git-svn for dev-vcs/subversion support The useflag seems to be ignored hoever. Reproducible: Always Steps to Reproduce: 1. USE="subversion" emerge git 2. git svn Actual Results: Error message stating: fatal: git was built without support for git-svn (NO_PERL=YesPlease). Expected Results: git-svn funktionality should be available
just for the record, the useflag is actualy shown as enabled: $ emerge -vp dev-vcs/git [ebuild R ] dev-vcs/git-1.7.3.2-r1 USE="bash-completion blksha1 curl gtk iconv subversion threads webdav -cgi -cvs -doc -emacs -perl (-ppcsha1) -tk -xinetd" 0 kB
It appears from the "(NO_PERL=YesPlease)" that this is because you built git with USE="-perl". Please read the emerge logs carefully, there is a warning message ("git-svn needs USE=perl, it won't work") if you attempt to build with USE="subversion -perl". If you need subversion support, please build with USE="perl".
should't the subversion useflag require the perl useflag then?
There is no method for one USE flag to depend on another. Here, the perl USE flag takes precedence because subversion requires perl. If the user has therefore explicitly asked for no perl, the user will get no subversion either. Having subversion pull in the perl packages would just spawn bug reports saying that even though USE="-perl", perl was still installed. There's no way of keeping everybody happy, so this is the best compromise available. The conflicting USE flag combination also provides a warning, so that users are aware of what the problem is and the most likely steps to solve it.
ok thanks for clarifing
