My two technical questions remained open, and I have a third one:
(1) Would it even be possible to deploy many MW extensions that are in
different top-level directories in one git repo without pulling
subdirectories from the repo individually? If not, then the deployment
of git-code on sites
Hi,
I am sceptical about this. I do not see the advantage of having SMW
extensions maintained outside the normal MW git repo. It creates yet
another system to be aware of. On top of it, by installing from this
repo the user would not be done, i.e. they would still need to
manually get e.g.
Hey,
Would it even be possible to deploy many MW extensions that are in
different top-level directories in one git repo without pulling
subdirectories from the repo individually?
Yes, you can get the whole repo in one go. So it'd be easier to get the
extensions, although this really is just a
On 19/07/12 11:22, Stephan Gambke wrote:
Hi,
I am sceptical about this. I do not see the advantage of having SMW
extensions maintained outside the normal MW git repo. It creates yet
another system to be aware of. On top of it, by installing from this
repo the user would not be done, i.e.
Hi.
On 19 July 2012 14:53, Markus Krötzsch mar...@semantic-mediawiki.org wrote:
Jeroen did not suggest to move outside of MW git. The idea is just to
combine several closely related repos into one.
Yes, but would it be a _normal_ repo?
How would the workflow be? Now you clone MW, then you get
Hey,
Having to sift through all the extensions downloded with the package and
now cluttering my extensions dir
You could always just get only those extensions you want from the release
distribution. And when using git, I'm sure there is a way to only have some
dirs visible to you :)
would it
