This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] RFC: removing figlet source from Xen

To: Ben Guthro <bguthro@xxxxxxxxxxxxxxx>, "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Subject: Re: [Xen-devel] RFC: removing figlet source from Xen
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Mon, 21 Apr 2008 19:08:28 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 21 Apr 2008 11:08:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <480CCF63.5010607@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acij2rLq8XhJrw/NEd2FCAAWy6hiGQ==
Thread-topic: [Xen-devel] RFC: removing figlet source from Xen
User-agent: Microsoft-Entourage/
What a rathole this could be. Let's cache the figlet output across builds
and add a 'make tarball' target which for now just:
 1. Runs figlet.
 2. Deletes figlet.
 3. tar czf ...

 -- Keir

On 21/4/08 18:31, "Ben Guthro" <bguthro@xxxxxxxxxxxxxxx> wrote:

> 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-d8cc605dd386091c8b6be97b8a43fb6a
>> 5d624ae1
>> 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.
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list