Jeff King <peff@xxxxxxxx> writes: > I was thinking that you would be self-contained inside the > contrib/mw-to-git directory, and therefore you would have to teach your > code how to install the Git module, and you could not longer just "cp > git-remote-mediawiki" into the right place to install it. > > But I think we have already crossed that bridge somewhat with Git.pm. > And if you add your module as perl/Git/MediaWiki.pm and use the existing > perl build system, then it is not any extra effort from the build > system. I'm not sure having perl/Git/MediaWiki.pm would be a good idea: this MediaWiki.pm would be really a mediawiki thing more than a Git thing, so the Git main tree probably want to stay away from it and keep it in contrib. But you should be able to use contrib/mw-to-git/perl/GitMediawiki.pm or something like that and chain to ../../perl/Makefile in contrib/mw-to-git/Makefile. Also, for now, git-remote-mediawiki works only after you run "make install" in Git's toplevel. I think that's ok, but it would be weird to be able to use/test git-remote-mediawiki only after doing a "make install" to deploy the new mediawiki Perl module. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html