summaryrefslogtreecommitdiffstats
path: root/meta/files/common-licenses/BitstreamVera
diff options
context:
space:
mode:
authorElizabeth Flanagan <elizabeth.flanagan@intel.com>2011-12-03 15:16:15 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-12-08 15:24:30 +0000
commitcb91ef9310a2450650ec880be6f0fc3a6e2d4a23 (patch)
tree9886b8bbf81cfb2aedc4825f61ae86c4fae7d2b2 /meta/files/common-licenses/BitstreamVera
parentc41b31e45161b16d4a792db208edfaafbc164611 (diff)
downloadpoky-cb91ef9310a2450650ec880be6f0fc3a6e2d4a23.tar.gz
license: manifest and license path
This is a fairly large commit, so I want to step through some of what this accomplishes: 1. Additional licenses I've added/modified/corrected some of the common licenses within OE-core in prep. for a major license audit. Most of these are in SPDX format. A few, there is no OSI equivalent. 2. Additional SPDX mappings I've added some additional SPDX mappings to account for removing some duplicate licenses. (ie GPL-2 and GPL-2.0 were the same) I've also remapped a few things to more accurately reflect what they should be pointing at. Note: Artistic/LGPL/GPL/MPL. Quite a few LICENSE fields list these licenses. They make no sense and need auditing. In a future commit I have some fixes to particularly egregious LICENSE fields, but a full audit should be done. I've listed to obvious candidates at: https://wiki.yoctoproject.org/wiki/License_Audit 3. License manifest We now have a license manifest generation that occurs in rootfs for everything BUT .deb. This requires the changes Paul Eggleton has done to rootfs_* particularly the list_installed_packages function. The manifest is accurate during a parallel bitbake now (Weee!) and is prime for my planned SPDX format manifest during the next period. 4. License manifest on image. We also want the ability to add licenses to the image. This functionality is also in base-files and will be stripped out in my next commit. The manifest is not added by default and is a two var setting in license.conf: If I want *just* the manifest on the image (small) then I set: COPY_LIC_MANIFEST = "1" This copies the manifest to: /usr/share/common-licenses/license.manifest If I want the actual PKG license text on the image (much larger) I need to set both both COPY_LIC_MANIFEST and COPY_LIC_DIRS in license.conf. This will create: /usr/share/common-licenses/(package name)/(licenses in LIC_SRC_URI) Word of warning. This can be larger than wanted depending on image and is probably ripe for linking licenses, but I ran out of time this week to get that done. 5. Custom License search path. We now have the ability to add licenses to the build without touching common-licenses. This is set via license.conf: LICENSE_PATH += "/path/to/custom/licenses" You want to make sure the license is unique. license.bbclass picks the first license it finds. (From OE-Core rev: 558b5043e1d5a36caff137093fd04abcf025af1c) Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/files/common-licenses/BitstreamVera')
-rw-r--r--meta/files/common-licenses/BitstreamVera160
1 files changed, 160 insertions, 0 deletions
diff --git a/meta/files/common-licenses/BitstreamVera b/meta/files/common-licenses/BitstreamVera
new file mode 100644
index 0000000000..e6f03aa57a
--- /dev/null
+++ b/meta/files/common-licenses/BitstreamVera
@@ -0,0 +1,160 @@
1Bitstream Vera Fonts Copyright
2
3The fonts have a generous copyright, allowing derivative works (as
4long as "Bitstream" or "Vera" are not in the names), and full
5redistribution (so long as they are not *sold* by themselves). They
6can be be bundled, redistributed and sold with any software.
7
8The fonts are distributed under the following copyright:
9
10Copyright
11=========
12
13Copyright (c) 2003 by Bitstream, Inc. All Rights Reserved. Bitstream
14Vera is a trademark of Bitstream, Inc.
15
16Permission is hereby granted, free of charge, to any person obtaining
17a copy of the fonts accompanying this license ("Fonts") and associated
18documentation files (the "Font Software"), to reproduce and distribute
19the Font Software, including without limitation the rights to use,
20copy, merge, publish, distribute, and/or sell copies of the Font
21Software, and to permit persons to whom the Font Software is furnished
22to do so, subject to the following conditions:
23
24The above copyright and trademark notices and this permission notice
25shall be included in all copies of one or more of the Font Software
26typefaces.
27
28The Font Software may be modified, altered, or added to, and in
29particular the designs of glyphs or characters in the Fonts may be
30modified and additional glyphs or characters may be added to the
31Fonts, only if the fonts are renamed to names not containing either
32the words "Bitstream" or the word "Vera".
33
34This License becomes null and void to the extent applicable to Fonts
35or Font Software that has been modified and is distributed under the
36"Bitstream Vera" names.
37
38The Font Software may be sold as part of a larger software package but
39no copy of one or more of the Font Software typefaces may be sold by
40itself.
41
42THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
43EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
44MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
45OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL
46BITSTREAM OR THE GNOME FOUNDATION BE LIABLE FOR ANY CLAIM, DAMAGES OR
47OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL,
48OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR
49OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE FONT
50SOFTWARE OR FROM OTHER DEALINGS IN THE FONT SOFTWARE.
51
52Except as contained in this notice, the names of Gnome, the Gnome
53Foundation, and Bitstream Inc., shall not be used in advertising or
54otherwise to promote the sale, use or other dealings in this Font
55Software without prior written authorization from the Gnome Foundation
56or Bitstream Inc., respectively. For further information, contact:
57fonts at gnome dot org.
58
59Copyright FAQ
60=============
61
621. I don't understand the resale restriction... What gives?
63
64Bitstream is giving away these fonts, but wishes to ensure its
65competitors can't just drop the fonts as is into a font sale system
66and sell them as is. It seems fair that if Bitstream can't make money
67from the Bitstream Vera fonts, their competitors should not be able to
68do so either. You can sell the fonts as part of any software package,
69however.
70
712. I want to package these fonts separately for distribution and
72sale as part of a larger software package or system. Can I do so?
73
74Yes. A RPM or Debian package is a "larger software package" to begin
75with, and you aren't selling them independently by themselves.
76See 1. above.
77
783. Are derivative works allowed?
79Yes!
80
814. Can I change or add to the font(s)?
82Yes, but you must change the name(s) of the font(s).
83
845. Under what terms are derivative works allowed?
85
86You must change the name(s) of the fonts. This is to ensure the
87quality of the fonts, both to protect Bitstream and Gnome. We want to
88ensure that if an application has opened a font specifically of these
89names, it gets what it expects (though of course, using fontconfig,
90substitutions could still could have occurred during font
91opening). You must include the Bitstream copyright. Additional
92copyrights can be added, as per copyright law. Happy Font Hacking!
93
946. If I have improvements for Bitstream Vera, is it possible they might get
95adopted in future versions?
96
97Yes. The contract between the Gnome Foundation and Bitstream has
98provisions for working with Bitstream to ensure quality additions to
99the Bitstream Vera font family. Please contact us if you have such
100additions. Note, that in general, we will want such additions for the
101entire family, not just a single font, and that you'll have to keep
102both Gnome and Jim Lyles, Vera's designer, happy! To make sense to add
103glyphs to the font, they must be stylistically in keeping with Vera's
104design. Vera cannot become a "ransom note" font. Jim Lyles will be
105providing a document describing the design elements used in Vera, as a
106guide and aid for people interested in contributing to Vera.
107
1087. I want to sell a software package that uses these fonts: Can I do so?
109
110Sure. Bundle the fonts with your software and sell your software
111with the fonts. That is the intent of the copyright.
112
1138. If applications have built the names "Bitstream Vera" into them,
114can I override this somehow to use fonts of my choosing?
115
116This depends on exact details of the software. Most open source
117systems and software (e.g., Gnome, KDE, etc.) are now converting to
118use fontconfig (see www.fontconfig.org) to handle font configuration,
119selection and substitution; it has provisions for overriding font
120names and subsituting alternatives. An example is provided by the
121supplied local.conf file, which chooses the family Bitstream Vera for
122"sans", "serif" and "monospace". Other software (e.g., the XFree86
123core server) has other mechanisms for font substitution.
124
125Show details Hide details
126
127Change log
128r2011 by mark.nickel on Mar 3, 2011 Diff
129
130Majority of Multi-Line text editing is in
131the commit. Also added some specific free
132fonts to replace the existing set as we
133need some additional font metrics that we
134use in the Text Editing rendering
135pipeline.
136
137You can see the font licenses in the
138editor/fonts folder under each font.
139
140Still have some cleanup to do to add the
141text formatting (left,right,center) as
142...
143
144Go to:
145Hide comments
146Show comments
147
148Older revisions
149All revisions of this file
150
151File info
152Size: 5953 bytes, 123 lines
153View raw file
154
155File properties
156
157svn:executable
158 *
159
160