[Bug 238367] Review Request: xu4 - Ultima IV recreated

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: xu4 - Ultima IV recreated
Alias: xu4

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238367





------- Additional Comments From mtasaka at ioa.s.u-tokyo.ac.jp  2007-05-10 13:56 EST -------
(In reply to comment #22)
> (In reply to comment #21)
> > Sorry to interrupt. I have not read the previous discussion
> > in detail, however my recognition is that the problem with
> > this package is:
> > 
> > * the package xu4 _itself_ has no license problem
> > * to use xu4 actually, xu4 needs some data and one (who
> >   uses xu4) has to download the data from some URL
> > * And the license of the data is in question
> > 
> 
> Correct, except that the license is not in question, it can be freely and
> legally downloaded, but may not be (re)distributed.

For xtide, the data can be downloaded _freely_, however
(as Patrice and me wrote in README.fedora) 
"their license restricts commercial redistribution and selling"
so we judged that the data part cannot be included into Fedora.

So from your comment this package is exactly the case of
xtide.

> 
> > Okay?
> > If so, this is exactly the case of "xtide" package which
> > I maintain and was reviewed by Patrice Dumas.
> > If my recognition is correct, please check the comment by Patrice
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211626#c32
> > and what we actually did in 
> > /usr/share/doc/xtide-common-2.9.3/README.fedora (in xtide-common
> > rpm).
> 
> Correct, this is the same. Except I created a python gtk gui app todo the
> downloading, 

We simply added a bash shell script to help to download the
data from the URL (/usr/sbin/xtide-get_harmonics-data.sh in
xtide-common) .
IMO this is also the same with xtide.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.