Re: [NEW] games/opentyrian
Note that pkg/README files should follow the layout of the example in ports/infrastructure/templates, and you'll need to regenerate the PLIST. On 15 March 2014 03:12:03 GMT+00:00, Juan Francisco Cantero Hurtado i...@juanfra.info wrote: On Fri, Mar 14, 2014 at 01:29:37PM +0100, Pascal Schmid wrote: On 03/14/2014 03:27 AM, Theo de Raadt wrote: That really doesn't mean anything. What we need is either an explicit release to the public domain, or a copyright notice with a license grant permitting distribution/modification/whatever is needed. An alternative would be to just package the game engine itself but avoid including the data; instead tell people (in MESSAGE or README) how to download and install it. For something to land in the our domain of software, it must either have the word Copyright or the words Public Domain. Without those words, the content has not been dragged into the right sphere, and all rights might still be privately held. Just to get this right: We can't include the data files - OK. But would it be OK to add a MESSAGE line to tell users how to download the files? Don't use a MESSAGE. Add a README file to the directory pkg and run make update-plist. I will import the port when you add the file. In case the website goes offline due to license reasons the port would be unusable.
Re: [NEW] games/opentyrian
On 03/14/2014 03:27 AM, Theo de Raadt wrote: That really doesn't mean anything. What we need is either an explicit release to the public domain, or a copyright notice with a license grant permitting distribution/modification/whatever is needed. An alternative would be to just package the game engine itself but avoid including the data; instead tell people (in MESSAGE or README) how to download and install it. For something to land in the our domain of software, it must either have the word Copyright or the words Public Domain. Without those words, the content has not been dragged into the right sphere, and all rights might still be privately held. Just to get this right: We can't include the data files - OK. But would it be OK to add a MESSAGE line to tell users how to download the files? In case the website goes offline due to license reasons the port would be unusable.
Re: [NEW] games/opentyrian
On Fri, Mar 14, 2014 at 01:29:37PM +0100, Pascal Schmid wrote: On 03/14/2014 03:27 AM, Theo de Raadt wrote: That really doesn't mean anything. What we need is either an explicit release to the public domain, or a copyright notice with a license grant permitting distribution/modification/whatever is needed. An alternative would be to just package the game engine itself but avoid including the data; instead tell people (in MESSAGE or README) how to download and install it. For something to land in the our domain of software, it must either have the word Copyright or the words Public Domain. Without those words, the content has not been dragged into the right sphere, and all rights might still be privately held. Just to get this right: We can't include the data files - OK. But would it be OK to add a MESSAGE line to tell users how to download the files? Don't use a MESSAGE. Add a README file to the directory pkg and run make update-plist. I will import the port when you add the file. In case the website goes offline due to license reasons the port would be unusable. -- Juan Francisco Cantero Hurtado http://juanfra.info
Re: [NEW] games/opentyrian
On Wed, Mar 12, 2014 at 07:39:29PM +0100, Pascal Schmid wrote: port of the DOS shoot-em-up Tyrian Tested on amd64 and macppc (both -current) I attached your ports with some changes. IMO, the ports are OK but I see a problem in data. Where the license says that we can distribute the tarball and the distfile? -- Juan Francisco Cantero Hurtado http://juanfra.info opentyrian.tar.gz Description: application/tar-gz
Re: [NEW] games/opentyrian
On 03/13/14 16:02, Juan Francisco Cantero Hurtado wrote: On Wed, Mar 12, 2014 at 07:39:29PM +0100, Pascal Schmid wrote: port of the DOS shoot-em-up Tyrian Tested on amd64 and macppc (both -current) I attached your ports with some changes. IMO, the ports are OK but I see a problem in data. Where the license says that we can distribute the tarball and the distfile? I'm not sure what you're asking here. I think there is some confusion because there is a license file inside the data .zip but the website it is downloaded from has the following: Tyrian has been released as freeware by Jason Emery. So I'm not entirely sure what that means for us in terms of distribution. But this was a neat little game to waste an afternoon with, so ok for me after the license question gets resolved. ~Brian
Re: [NEW] games/opentyrian
On 2014/03/13 17:09, Brian Callahan wrote: On 03/13/14 16:02, Juan Francisco Cantero Hurtado wrote: On Wed, Mar 12, 2014 at 07:39:29PM +0100, Pascal Schmid wrote: port of the DOS shoot-em-up Tyrian Tested on amd64 and macppc (both -current) I attached your ports with some changes. IMO, the ports are OK but I see a problem in data. Where the license says that we can distribute the tarball and the distfile? I'm not sure what you're asking here. I think there is some confusion because there is a license file inside the data .zip but the website it is downloaded from has the following: Tyrian has been released as freeware by Jason Emery. That really doesn't mean anything. What we need is either an explicit release to the public domain, or a copyright notice with a license grant permitting distribution/modification/whatever is needed. An alternative would be to just package the game engine itself but avoid including the data; instead tell people (in MESSAGE or README) how to download and install it.
Re: [NEW] games/opentyrian
On Thu, Mar 13, 2014 at 05:09:15PM -0400, Brian Callahan wrote: On 03/13/14 16:02, Juan Francisco Cantero Hurtado wrote: On Wed, Mar 12, 2014 at 07:39:29PM +0100, Pascal Schmid wrote: port of the DOS shoot-em-up Tyrian Tested on amd64 and macppc (both -current) I attached your ports with some changes. IMO, the ports are OK but I see a problem in data. Where the license says that we can distribute the tarball and the distfile? I'm not sure what you're asking here. I think there is some confusion because there is a license file inside the data .zip but the website it is downloaded from has the following: Tyrian has been released as freeware by Jason Emery. So I'm not entirely sure what that means for us in terms of distribution. But this was a neat little game to waste an afternoon with, so ok for me after the license question gets resolved. Just to clarify. Pascal, we need to know if we can distribute the distfile from the openbsd servers and packaging the content of the distfile. The comment above of PERMIT_* in data needs more info about the permissions. If it is not possible, you can add a README file to the opentyrian port with the instructions to download and install the data files. -- Juan Francisco Cantero Hurtado http://juanfra.info
Re: [NEW] games/opentyrian
Hi Juan Francisco, Juan Francisco Cantero Hurtado wrote on Thu, Mar 13, 2014 at 09:02:11PM +0100: On Wed, Mar 12, 2014 at 07:39:29PM +0100, Pascal Schmid wrote: port of the DOS shoot-em-up Tyrian Tested on amd64 and macppc (both -current) I attached your ports with some changes. IMO, the ports are OK They work on i386, too. but I see a problem in data. Where the license says that we can distribute the tarball and the distfile? All i can find is the vague sentence Tyrian has been released as freeware by Jason Emery. http://www.camanis.net/ The following one isn't much clearer either - no names, no dates, nothing specific, not even the actual file our port is downloading: http://www.freewebs.com/worldtreegames/ The following may or may not be free, but it's not what we want to distribute, either: http://www.lostgarden.com/2007/04/free-game-graphics-tyrian-ships-and.html So the following questions seem unanswered so far: * Whether camanis.net and/or www.freewebs.com are allowed to speak on behalf of Jason Emery; otherwise, this would merely be heresay. * Whether Jason Emery is allowed to speak on behalf of Epic MegaGames, the company mentioned in the license.doc file inside the zipball, which is a fully commercial EULA. * It seems other authors were involved. So it is unclear whether Jason Emery has their consent, or doesn't need it for whatever reason. * Even if all the above would hold true, that vague sentence doesn't necessarily imply a license for redistribution. Apparently, the OpenTyrian developers are bold enough to include the data files into their Windows binary bundle, see here: https://code.google.com/p/opentyrian/wiki/Downloads But clearly, *they* don't own the Copyright, so we cannot conclude much from that. So, i'd suggest to play it safe and use the following for the opentyrian-data port: # http://www.camanis.net/ - whoever that is - merely says: # Tyrian has been released as freeware by Jason Emery. PERMIT_PACKAGE_CDROM = license unclear PERMIT_PACKAGE_FTP =license unclear PERMIT_DISTFILES_FTP = license unclear With that, consider this an ok schwarze@. Yours, Ingo
Re: [NEW] games/opentyrian
On 2014/03/13 17:09, Brian Callahan wrote: On 03/13/14 16:02, Juan Francisco Cantero Hurtado wrote: On Wed, Mar 12, 2014 at 07:39:29PM +0100, Pascal Schmid wrote: port of the DOS shoot-em-up Tyrian Tested on amd64 and macppc (both -current) I attached your ports with some changes. IMO, the ports are OK but I see a problem in data. Where the license says that we can distribute the tarball and the distfile? I'm not sure what you're asking here. I think there is some confusion because there is a license file inside the data .zip but the website it is downloaded from has the following: Tyrian has been released as freeware by Jason Emery. That really doesn't mean anything. What we need is either an explicit release to the public domain, or a copyright notice with a license grant permitting distribution/modification/whatever is needed. An alternative would be to just package the game engine itself but avoid including the data; instead tell people (in MESSAGE or README) how to download and install it. For something to land in the our domain of software, it must either have the word Copyright or the words Public Domain. Without those words, the content has not been dragged into the right sphere, and all rights might still be privately held.
