[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] RFC: removing figlet source from Xen
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 ...
On 21/4/08 18:31, "Ben Guthro" <bguthro@xxxxxxxxxxxxxxx> wrote:
> Alternately - a clone could be used:
> 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:
>> 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...
> Xen-devel mailing list
Xen-devel mailing list