REQUEST: MakeMKV *official* Repository! :)

[glubsch]

Hi there, folks!

As we all agree, MakeMKV is one of the best programs to be found out there. And the best feature of it all - it?s FREE (at least right now).
For me, it is *THE* tool for backing up DVDs and doing all kind of crazy stuff. It absolutely _rocks_.

I?ve been talking to Mike Chen on the Doom9-Forums if he would mind if I asked the Packman-Team to create an official Repository for MakeMKV that is usable within OpenSUSE. Result actually was that he didn?t mind and would welcome that idea. Best of all, he offered "all necessary assistance" as well as his email address for faster communication. THANKS, MIKE!

Recently searching the net, I stumbled across the packmans mail archive - including some interesting replies. Check it out HERE.
As always, one has to check whether the licensing permits distribution and/or modification of files before creating anything.

I?ll quote a conclusion of their findings here:

> I went to the MakeMKV websifte and downloaded the source code for MakeMKV.
> Nowhere on the site could I find any mention of what license is used. All I see is info about it being a time limited demo.
> From looking through the source files I find some evidence that it may be under a mix of licenses ( lgpl, public domain etc).
> It would be nice if this was more clear.

----

This part is - as a whole - under the LGPL (I did not check the license for every single file, but at least it looks as if it were LGPL).
The binary part - that is necessary to run the program - is (c) GuinpinSoft inc and distribution is not allowed (src/eula_en_linux.txt).

Is this all the truth to it? This might be the point that keeps the project from even starting...
And here?s the big question: How would the Packman-Team be able to create a Repository without hurting any Licenses?

So, if Packman would not be allowed to create a MakeMKV-Repo, I?d suggest that MakeMKV themselve provides an official one. VOTE 4 IT!
I?m sure many of you would appreciate an official Repo for MakeMKV that works with a variety of Distros and not just OpenSUSE.

Please feel free to throw your thoughts and comments into this thread. Thanks.

-glubsch

[glubsch]

Hahaha... more than 160 people watching this thread and noone is able to share their opinion. That rocks. C?mon!

[nille]

I also wondered about the licens and the source didn't include any License (accept file headers).
Looking at the files it looks to be like this:

libabi OpenSSL and also LGPL on the diffrent files and nowhere did i see anything mentioning about OpenSSL Project and OpenSSL Toolkit as the openssl license demand.
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)" http://www.openssl.org/source/license.html

libdriveio LGPL and public domain

libebml LGPL http://dl.matroska.org/downloads/libebml

libmakemkv LGPL

libmatroska LGPL http://www.matroska.org http://matroska.org/node/47

makemkvgui Mozilla Public License http://www.mozilla.org/MPL

msvc LGPL and public domain

sstring public domain


Why doesn't MakeMKV ship any License text with the source?
And where can the latest 1.4.9 source code be downloaded? (since i can only find the one for makemkv_v1.4.8_beta_oss)
Or is it the same unmodified source as the 1.4.8_beta?
So there's an lack of information, not that big of a problem but still it should be addressed. (i find it confusing right now)
Other than that keep up the good work.

[glubsch]

Thanks for sharing, nille. As you can see, releases can normally be downloaded from the MakeMKV main website.
Obviously the developers didn?t change the Links for the Linux sources yet - but that?s no problem. Just replace the version numbers.

Ok, don?t move your fingers - here ya go:

http://www.makemkv.com/download/makemkv ... bin.tar.gz
http://www.makemkv.com/download/makemkv ... oss.tar.gz

The rest of the procedure remains to be the same as always. But I really wonder if they could provide a repository for their great tool...
Mike, if you are reading this - I?d like to receive an official statement on this request.

Happy compiling, nille!

-glubsch

[mike admin]

Thank yo for taking time and registering on this forum, I do appreciate it. Generally, we would do everything necessary to resolve all license issues.

libabi OpenSSL and also LGPL on the diffrent files and nowhere did i see anything mentioning about OpenSSL Project and OpenSSL Toolkit as the openssl license demand.
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)" http://www.openssl.org/source/license.html

I believe attribution applies only if source code is not provided, but I might be wrong.

libdriveio LGPL and public domain
libebml LGPL http://dl.matroska.org/downloads/libebml
libmakemkv LGPL
libmatroska LGPL http://www.matroska.org http://matroska.org/node/47
makemkvgui Mozilla Public License http://www.mozilla.org/MPL
msvc LGPL and public domain
sstring public domain

This is correct. Package-wise I would suggest 3 packages - libdriveio, libmakemkv ang makemkvgui. Also please note that "our" libebml and libmatroska contain additional changes, so regular libraries can't be used instead.

Why doesn't MakeMKV ship any License text with the source?

Since it is entirely open source and each file contains applicable license in header. Is package required to have a license file? How does it work when multiple licenses apply?

And where can the latest 1.4.9 source code be downloaded?

You've managed to come here precisely at a day when program was released but forum was not yet updated.

Also on a DL you've mentioned a lack of distribution clause in makemkv binary package license - it is a concern? Is there any particular clause that we can add to the license that will resolve it?

[nille]

Thanks allot for your answers

Since it is entirely open source and each file contains applicable license in header. Is package required to have a license file? How does it work when multiple licenses apply?

As far as i know the license in the headers is enough for the license claim, but an license file makes the overview a hole lot easier and less confusing since you get an quick overview.

I believe attribution applies only if source code is not provided, but I might be wrong.

I'm not sure since i heard so many versions about it. But when i read the license it's my understanding that it's needed.
But an quick mail to the OpenSSL team should answer it.

You've managed to come here precisely at a day when program was released but forum was not yet updated.

How typical Well i found the sources now

[glubsch]

Hey boys! I?ve been wondering why there hasn?t been as much participation as thought at first...
When will MakeMKV turn commercial, Mike? The Packman-Team does not seem to be responding either (yet).

Let me know if there are things that have to be cleared out of the way in order to build a working repository for MakeMKV.

-glubsch