Packaging Questions - Githubissues

libretro / parallel-n64

Optimized/rewritten Nintendo 64 emulator made specifically for Libretro. Originally based on Mupen64 Plus.

327 stars 128 forks source link

Packaging Questions #489

Open ryan-sg opened 6 years ago

ryan-sg commented 6 years ago

Hi! This n64 core is really nice. Good job getting this together! I am trying to make a package for this for OpenBSD, and have run into two little problems:

There is no release, or anything tagged. What version can I call this? Is it working toward a 1.0? I can provide a pseudo version number but if there is already a plan I'd rather make sure I follow what is planned.
License. I see mupen64plus parts licensed under GPLv2, and I see MAME license on some of the angrylion stuff, and the gliden64 directory I couldn't find anything for license at all. OpenBSD marks down license info in the port files that create the package, to help handle whether a package can be distributed publicly with the rest of the packages. Clarification here would be gratefully appreciated.

hizzlekizzle commented 6 years ago

Licensing for GLideN64 is kind of a mess. As I recall, it is based partially on gln64, which never had a proper license, and on several other GPL-licensed plugins. I think people have just accepted it as being GPL and none of the original rightsholders have complained otherwise...

bentley commented 6 years ago

Unfortunately OpenBSD can’t provide binary packages for parallel-n64. We can’t accept GLideN64’s GPLv2 claim since it’s based on gln64, which is all rights reserved until explicitly said otherwise by Orkin…

That’s a shame but I don’t see any alternative except perhaps all the gln64 parts being cleanly rewritten.

We can provide a port for people to compile from source though. A tagged release (or prerelease) would be helpful for that, and greatly appreciated on our end.

hizzlekizzle commented 6 years ago

Seems like a good solution. I personally think it's weird that so many people have just accepted the GLideN64 licensing, so I don't blame you at all for avoiding it.

I'll talk to the gang and see about tagging.

ryan-sg commented 6 years ago

Thanks @hizzlekizzle and @bentley for weighing in on the situation. Presently marked the port as '2.0rc2' , as I discovered the plugin returns this version when the core is loaded in retroarch.

bentley commented 6 years ago

Any decision on whether/when to tag a release?

ghost commented 6 years ago

Problem is Orkin has been AWOL for years. So has Rice and all the others.