On 02/10/2013 15:42, "Daniel Kinzler" <daniel.kinzler(a)wikimedia.de>
wrote:
Am 01.10.2013 20:14, schrieb Tom Morris:
How about not creating a fork just so you can
delete a couple of
directories? The full download is a whopping 260KB. Is that really too
big/complex to include in its entirety and just ignore the parts you
don't
use?
Not deploying code we do not use, especially if it is complex, is a
requirement
from the ops team. And deploying a standalone HTTP end point (as
contained in
the EasyRDF distribution) on the boxes that server Wikipedia is an
absolute no
go. We had the choice of either deleting the unneeded parts, or writing
our own.
This is actually not the first time I'm having this problem with an RDF
library
when all I want to do is export. Last time, I ended up writing my own (in
Java).
-- daniel
Hello,
Making EasyRdf more modular, making it possible to only use the parts that
you need, is definitely on my roadmap. I think RDF.rb does this very well.
Although it is a difficult to balance up against keeping it easy to
install and use.
In the meantime, would it help to have a script that automatically creates
a cut down version of EasyRdf from the git repo?
nick.
-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------