The svn ebuilds inheriting mythtv-plugins checkout the 'mythplugins' directory from the repo into /usr/portage/distfiles/svn-src/<plugin_name>/mythplugins . This is redundant - mythtv users on svn might (and probably will) have several plugins installed at once. It puts extra strain on their svn server and takes up more room on my HDD. It would be good if all the mythtv-plugins shared the same svn checkout of mythplugins. One possible way to do this is to add the following line to the top of mythtv-plugins.eclass : ESVN_PROJECT="" From what I understand from reading subversion.eclass, the source will be checked out to: ${ESVN_STORE_DIR}/${ESVN_PROJECT}/${ESVN_REPO_URI##*/} Given that ${ESVN_REPO_URI} for a plugin is something like "mythplugins/mythvideo", if we set ${ESVN_PROJECT} to a blank string, we would get a directory like: /usr/portage/distfiles/svn-src//mythplugins/mythvideo/ While perhaps this is a bit of a bastardisation (the whole double slash thing), it does ensure that all mythtv-plugins get checked out to the same directory. This is my first bug report so please let me know if I've stuffed something up. Reproducible: Always Steps to Reproduce: Install a 'pre' (svn) version of a mythtv plugin. Actual Results: Source gets checked out to a separate directory. Expected Results: Source gets checked out to a directory common to all mythtv-plugins. Possible solution - add to the top of mythtv-plugins.eclass : ESVN_PROJECT=""
Also, mythmovies needs to be added to the list of mythplugins so that it's not built (guess this is a known issue because it's pretty recent, but thought I should mention it anyway. if version_is_at_least "0.21_pre" ; then MYTHPLUGINS="${MYTHPLUGINS} mythmovies mythzoneminder" fi (and mythdvd can be removed, but that's in a separate bug here: http://bugs.gentoo.org/show_bug.cgi?id=180696 )
Something doesn't work for you? If so, let us know. Otherwise, the point of this bug is exactly what?
(In reply to comment #2) > Something doesn't work for you? If so, let us know. Otherwise, the point of > this bug is exactly what? The point of this bug is to improve the behaviour of the eclass. Hence why I filed it as 'enhancement'. Is there something the matter with submitting enhancements?
Why'd this get closed?
I like the suggestion.
Fixed. Nice suggestion Tom. Sorry for not getting back to you via e-mail. I've been moving and without my mail server for about a week.
