I think this is already off-topic... but anyway. On Thu, Apr 2, 2015 at 1:01 AM, Stian Soiland-Reyes <[email protected]> wrote: > > BTW (I had a quick go at this) if you try to package Jena for Debian > (the "proper" way to be included in the distro, not the /opt/jena > way), then all Maven dependencies must also be from Debian packages, > as the special mvn-debian command disallows downloading from Maven > Central to force everything to be from Debian-built binaries. >
You should not get extra binaries in the installation process, but is a quite common practice for those packages that need to retrieve stuff that can't not be distributed according the Debian policies. The typical example are packages as ttf-mscorefonts-installer. But I guess Fuseky and any Jena packages is in that situation. Read bellow. > It's doable, at least for the core of Jena which has not got a lot of > dependencies. Fuseki (which is also very interesting as a Debian > package) would take some more effort. Elephas would be hard, as > hadoop is not in Debian. You could use the same approach we followed to package Marmotta, which is available since few releases via stack.linkeddata.org. If you find it interesting, let's move this discussion to dev@jena. Cheers, -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 6602747925 e: [email protected] w: http://redlink.co
