From: Ben Guthro <bguthro@virtualiron.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: RFC: removing figlet source from Xen
Date: Mon, 21 Apr 2008 13:31:15 -0400 [thread overview]
Message-ID: <480CCF63.5010607@virtualiron.com> (raw)
In-Reply-To: <20080416210104.GM1444@redhat.com>
Alternately - a clone could be used:
http://freshmeat.net/projects/toilet/
http://libcaca.zoy.org/toilet.html
(LGPL)
Daniel P. Berrange wrote:
> The Xen source tree currently contains a copy of the figlet sources. During
> the hypervisor build it builds figlet and uses it to generate the big ascii
> art 'Xen 3.1.0' version string shown upon boot.
>
> The problem is that the figlet code is licensed under the original Artistic
> 1.0 license, and not the clarified version. The original non-clarified
> license is classed as non-free by Debian and on the forbidden list for
> Fedora too:
>
> http://fedoraproject.org/wiki/Licensing#head-d8cc605dd386091c8b6be97b8a43fb6a5d624ae1
>
> So, the figlet source code in Xen has to be removed if we're to continue
> shipping Xen in Fedora. While I could re-spin the source tar.gz files myself
> before importing them to Fedora, it'd be preferrable if the official Xen
> source code tar.gz were shipped without figlet in the first place.
>
> I'm happy to send a patch to clean this up - just wondering which option
> would be preferred...
>
> - Remove figlet entirely and just have a normal size "Xen 3.1.0" string
> printed at boot
> - Include the pre-generated large ascii art "Xen" and have normal size
> "3.1.0" version stirng.
> - Optionally call out to a plain figlet binary in $PATH, using a normal
> size version string if not found.
>
> Personally I'd just go for option 1 or 2 since they're least effort...
>
> Dan.
>
next prev parent reply other threads:[~2008-04-21 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 21:01 RFC: removing figlet source from Xen Daniel P. Berrange
2008-04-21 17:31 ` Ben Guthro [this message]
2008-04-21 18:08 ` Keir Fraser
2008-04-21 18:24 ` Daniel P. Berrange
2008-04-21 18:26 ` Keir Fraser
2008-04-21 19:05 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=480CCF63.5010607@virtualiron.com \
--to=bguthro@virtualiron.com \
--cc=berrange@redhat.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.