Extraction of Reusable Structured Data from Wikipedia
In this article, it is said that there is wmf4, mediawiki distribution including all the wikipedia extensions, but I can't find it.
There is no pre-built package with all extensions used in Wikimedia wikis, so the easiest way would be to clone the latest wmf-branch of MediaWiki (which is thought to be used in Wikimedia wikis and/or experienced users, only and may contain bugs for third party users) from the git repository and initialize the git submodules. So, to use the latest wmf version, 1.27.0-wmf.1, (which is currently used on Wikimedia test wikis, only, see the roadmap for the actual deployment status) you coulduse git:
git clone https://gerrit.wikimedia.org/r/mediawiki/core
cd core
git checkout wmf/1.27.0-wmf.1
git submodule update --init
After that you should have the actual copy of MediaWiki in the core directory (you can look at the contents on github, too). But think about, that wmf-versions aren't officially supported by the MediaWiki developers, but we welcome any bug report.
Btw.: You could clone the latest stable version (currently MediaWiki 1.25.X) and install all extensions you want, manually. A list of actual deployed extensions to Wikimedia wikis can be found here.
git clone https://gerrit.wikimedia.org/r/mediawiki/extensions
cd extensions
git submodule update --init
gets you all extensions hosted in Wikimedia's git repo. It's unlikely to be useful though. Also, I don't think extensions that are not used by Wikimedia have wmf/... branches.
Related
Window Tortoisehg, realized I cannot use Bitbucket, is there free alternative for home use (with a cheap annual subscription) that is easy to setup. Many answer found here are outdated since Bitbucket no longer support Tortoisehg. I'm open for suggestion. I looked into GitHub but had no luck in making push works
You still can use Bitbucket and any other Git-hosting with hg-git extension in Mercurial (ssh and https pushes aren't a problem at all - I have and use Github repos from my THG)
You can see at pure Mercurial hostings, but I'll recommend starting from
Helix TeamHub (free)
SF.net (terrible old interface, but..)
Heptapod Hosting (paid, but not overpriced)
Heptapod is one commercial (not free) example. They say:
The power of GitLab Core and Mercurial combined ... Access your
Mercurial repository through HTTPS, SSH or the Web UI.
One side-benefit of using their services is that they themselves host the repositories for numerous Mercurial tools including TortoiseHG, etc. Perhaps / presumably the commercial side helps to financially support all of that:
https://foss.heptapod.net/explore/projects/trending
I've enabled the Mercurial forest extension:
hgext.forest=
But the command 'fclone' is still not found.
I guess the extension is not installed.
How can I install the forest extension on Kubuntu 11.04? (I'm using Mercurial v2.2.1)
/usr/share/mercurial contains the hgk and hgext.rc scripts, so is this the hgext directory?
How can I get the forest script? I searched in KPackageKit but I couldn't find it...
From the Mercurial wiki:
This third-party extension does not appear to be actively maintained. Consider using subrepos instead.
This extension is not being distributed along with Mercurial.
Background:
I want to check-out the source code from Cliche, which is stored in a Mercurial repository. I use NetBeans 7 with JDK 1.7 on Windows, but have no experience with Mercurial. I only want to get the source code, further usage of Mercurial is not required.
Question: What software / plug-in, etc. do I need to install, if any, to perform the above task?
You will find the installation process and first checkout in: "Mercurial User Guide".
(You need to install Mercurial itself first)
And more on Mercurial used from Netbeans on "NetBeans + Mercurial Training".
I am a bit new to hg and while I am familiar with the python-based repo tool (used in project like the Android Open Source Project) I am not aware of one for Mercurial. Is there such a tool for hg?
I'm not very familiar with repo, but my understanding was that it allowed them to construct a project out of lots of smaller repositories.
If that's the case then it's just built in. Subrepositories.
Edlund was kind enough to open-source their repoman tool, which was directly inspired by the Android project's repo tool as I understand the history.
I have an existing Mercurial repository for a C++ application in a small corporate environment. I asked a co-worker to add the setup script to the repository and he added all of the dependency binaries, PDFs, and executable to the repository under an Install directory. I dislike having the binaries and dependencies in the same repository, but I'd like recommendations on best practices. Here are the options I am considering:
Create a separate repository for the
Installer and related files
Create a subrepository for the
Installer and related files
Use a (yet to be identified) build
dependency manager
I am concerned with using a subrepository with Mercurial based on what I've read so far and the (apparently) incomplete implementation. I would like to get a project dependency system, e.g. Ivy, but I don't know all of the options and haven't had time yet to try out any options.
I thought I'd use TortoiseHg as a basis, and it does not have the TortoiseHg binaries in the repository although it does have some binaries such as kdiff3.exe. Instead it uses setup.py to clone multiple repositories and build the apps. This seems reasonable for OSS, but not so much for corporate environments.
Recommendations?
I've had great luck using a good dependency manager, but it's more useful for code modules than artifacts. A sub-repo certainly works, but you'll not be cutting the clone time of people pulling the top tree since it will cascade into the subrepo too.
Someone will probably suggest using bfiles or big files, but I'd avoid it. They work well enough, but that functionality looks like it's going into mercurial this summer natively at which time those will languish.
Were I you I'd (a) hit the co-worker (b) try to strip those added files (using strip or convert), (c) re-do it will the installers being built not stored.
The PDFs I'd probably store, but there are some neat tricks for generating docs if you're interested.