Hi Jeroen, this works. SubPageList is no problem too.
I got Semantic MediaWiki (Version 1.9 beta-1) incl. DataValues DataValues (Version 0.1.1) Collection of objects representing various kinds of values Jeroen De Dauw DataValues Geo (Version 0.1) Geographical value objects, parsers and formatters Jeroen De Dauw and The Wikidata team DataValues Number (Version 0.1) Numerical value objects, parsers and formatters The Wikidata team DataValues Time (Version 0.1) Time value objects, parsers and formatters The Wikidata team DataValues Validators (Version 0.1) Contains common ValueValidator implementations Jeroen De Dauw and The Wikidata team DataValuesCommon (Version 0.1.1) Contains common implementations of the interfaces defined by DataValuesInterfaces Jeroen De Dauw and The Wikidata team DataValuesInterfaces (Version 0.1.2) Defines interfaces for ValueParsers, ValueFormatters and ValueValidators Jeroen De Dauw Other But some extensions are now in wikiroot/vendor others in wikiroot/extensions What about: include_once( __DIR__ . '/vendor/autoload.php' ); Befor I begin to make my extensions composer compatible I want to make clear what I have to include. In the entry point of SMW it tries to include autoload with: include_once( __DIR__ . '/vendor/autoload.php' ); ...but in extensions/SemanticMediawiki resist no "autoload.php". ...does... "autoload": { "files": ["MyExtension.php"] ...mean I'am a substitution of "autoload.php"? By the way after installing subpages in a second turn SMW was uninstalled! ;-). Might be because of my composer.json...I replaced the require statements. Any ideas how to implement partial updates and different repositories? cheers. -----Ursprüngliche Nachricht----- Von: Jeroen De Dauw [mailto:jeroended...@gmail.com] Gesendet: Dienstag, 26. November 2013 02:09 An: Lists Cc: Semantic MediaWiki developers Betreff: Re: [SMW-devel] raising composer features Hey Lists, If you are getting an error because git is not installed, we, that sucks. I was under the impression Composer would be smart enough to get the code as tarball in such a case. Though perhaps it normally is, and simply cannot do this in your case, as you are likely specifying dev-master (which refers to the master branch on git) to be installed. Two things I suggest trying, that might get around this issue: * add the --prefer-dist flag at the end of your Composer install command when running it. This will get packages as tarballs when available. * rather then using "dev-master" as version, use "*" In any case, I highly suspect that this will not occur when specifying 1.9 once it has been released. You can try installing version 1.0 the SubPageList extension [0] and see if you run into the same issue or not. [0] https://github.com/wikimedia/mediawiki-extensions-SubPageList Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel