aboutsummaryrefslogtreecommitdiffstats
path: root/classes
AgeCommit message (Expand)Author
2009-02-20efl: force arm insturctions, not thumb to stop illegal instruction bugs.Carsten Haitzler (Raster
2009-02-17base.bbclass: output messages only if BitBake 1.8 is used (from Poky)Marcin Juszkiewicz
2009-02-17failure-cleanup.bbclass: class that does -c clean on a package that fails to ...Koen Kooi
2009-02-14icecc.bbclass: base fix for cross and native builds, patch/9Roman I Khimov
2009-02-13package_ipk.bbclass: Add missing : from a045dfacf6f2541e0f410d9d109581f181303756Tom Rini
2009-02-13Merge branch 'master' of git://projetos.ossystems.com.br/git/users/otavio/org...Otavio Salvador
2009-02-13package.bbclass, package_ipk.bbclass: add dynamic depends on locale packages ...Otavio Salvador
2009-02-11sanity.bbclass: do not fail if /bin/sh is not symlinkMarcin Juszkiewicz
2009-02-10module_strip: When picking module suffix, use KERNEL_MAJOR_VERSION.Tom Rini
2009-02-10module-base: Fix the test on KERNEL_OBJECT_SUFFIXTom Rini
2009-02-07autotools_stage.bbclass: merge from pokyKoen Kooi
2009-02-04insane.bbclass: Fix MIPS and GNU_HASH check.Tom Rini
2009-02-04sanity.bbclass: make a warning about dash being used as /bin/sh (from Poky)Marcin Juszkiewicz
2009-02-03base.bbclass: only error out on missing checksums when OE_STRICT_CHECKSUMS is...Koen Kooi
2009-02-03dietlibc: introduce dietlibc to openembeddedwoglinde
2009-01-30rootfs_deb.bbclass : fix merge problems where I removed ${libdir}Graeme Gregory
2009-01-30package_deb.bbclass, rootfs_deb.bbclass : merge in poky changes to these clas...Graeme Gregory
2009-01-30kernel.bbclass: move initramfs stuff to configure so we can do postprocessing...Koen Kooi
2009-01-28Merge branch 'org.openembedded.dev' into trini/canadian-final-mergeTom Rini
2009-01-28package_ipk.bbclass: Add and use IPKGCONF_CANSDK.Tom Rini
2009-01-27Merge trini/canadian-merge branch into org.openembedded.dev, fixup aTom Rini
2009-01-27module.bbclass: add common make options to module_do_install()Cliff Brake
2009-01-25kernel.bbclass: Remove some repetition in last commit.Tim 'timtim' Ellis
2009-01-25kernel.bbclass: Add missing entry for scsi headers in staging, as needed by i...Tim 'timtim' Ellis
2009-01-22sanity.bbclass: Provide preserving the mmap_min_addr setting over reboots (fr...Richard Purdie
2009-01-20lsppc: Remove foonas classes lsppchg-image and lsppchd-imageTim 'timtim' Ellis
2009-01-20image.bbclass: resize images (ext2/ext3) only if they are bigger then IMAGE_R...Denys Dmytriyenko
2009-01-20Auto resizing ext2/ext3 images (from Poky)Marcin Juszkiewicz
2009-01-19package.bbclass: skip symlinks when generating shlib info in package_do_shlibs()Denys Dmytriyenko
2009-01-18gnome.bbclass: inherit gtk-icon-cacheKoen Kooi
2009-01-17n2100-image.bbclass: Fix usage of tail so image post worksTim 'timtim' Ellis
2009-01-16SDK: Rename 'SDK_PREFIX' to 'SDK_PATH' so that it has a meaning analogous to ...Tom Rini
2009-01-16canadian sdk: Add classes/canadian{,-cross,-native,-sdk}.bbclassTom Rini
2009-01-16insane.bbclass: Fix thinko in package_qa_check_staged logic for iscrossnativeTom Rini
2009-01-16insane.bbclass: Add handling for canadian classesRichard Purdie
2009-01-16bitbake.conf: Add EXEEXT variables for BUILD/HOST/TARGET so we can start to h...Richard Purdie
2009-01-16siteinfo.bbclass: Add cygwin and mingw entriesRichard Purdie
2009-01-16Merge branch 'rpurdie/canadian-sofar' into org.openembedded.devTom Rini
2009-01-17distutils.bbclass: only remove if existingMichael 'Mickey' Lauer
2009-01-17distutils.bbclass: bandaid against wrong datadir installationMichael 'Mickey' Lauer
2009-01-15base.bbclass: Add subdir feature to SRC_URI entries.Robert Schuster
2009-01-15{e,efl}.bbclass: we want all the speed we can get out of it *and* it SIGILLs ...Koen Kooi
2009-01-13package_tar.bbclass: fix traceback for empty packageMichael 'Mickey' Lauer
2009-01-12kernel.bbclass: do not use insecure tmpnam() function for generating unique n...Marcin Juszkiewicz
2009-01-12autotools.bbclass: adding do_install_append() to autotools.bbclassjohn_lee/openmoko-toolchainJulian_chu
2009-01-10insane.bbclass: Fix thinko in package_qa_check_staged logic for iscrossnativeTom Rini
2009-01-09insane.bbclass: Add handling for canadian classesRichard Purdie
2009-01-09bitbake.conf: Add EXEEXT variables for BUILD/HOST/TARGET so we can start to h...Richard Purdie
2009-01-09siteinfo.bbclass: Add cygwin and mingw entriesRichard Purdie
2009-01-06module.bbclass: pass KERNELDIR as wellKoen Kooi
t/ar_srcuri'>rbt/ar_srcuri OpenEmbedded Core user contribution treesGrokmirror user
summaryrefslogtreecommitdiffstats
path: root/meta/files/common-licenses/YPL-1.1
blob: 4a1880aa12ca68e1dd5fdd7549b06a568acbf2f2 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Yahoo! Public License, Version 1.1 (YPL)
This Yahoo! Public License (this "Agreement") is a legal agreement that describes the terms under which Yahoo! Inc., a Delaware corporation having its principal place of business at 701 First Avenue, Sunnyvale, California 94089 ("Yahoo!") will provide software to you via download or otherwise ("Software"). By using the Software, you, an individual or an entity ("You") agree to the terms of this Agreement.

In consideration of the mutual promises and upon the terms and conditions set forth below, the parties agree as follows:

Grant of Copyright License
1.1 - Subject to the terms and conditions of this Agreement, Yahoo! hereby grants to You, under any and all of its copyright interest in and to the Software, a royalty-free, non-exclusive, non-transferable license to copy, modify, compile, execute, and distribute the Software and Modifications. For the purposes of this Agreement, any change to, addition to, or abridgement of the Software made by You is a "Modification;" however, any file You add to the Software that does not contain any part of the Software is not a "Modification."
1.2 - If You are an individual acting on behalf of a corporation or other entity, Your use of the Software or any Modification is subject to Your having the authority to bind such corporation or entity to this Agreement. Providing copies to persons within such corporation or entity is not considered distribution for purposes of this Agreement.
1.3 - For the Software or any Modification You distribute in source code format, You must do so only under the terms of this Agreement, and You must include a complete copy of this Agreement with Your distribution. With respect to any Modification You distribute in source code format, the terms of this Agreement will apply to You in the same way those terms apply to Yahoo! with respect to the Software. In other words, when You are distributing Modifications under this Agreement, You "stand in the shoes" of Yahoo! in terms of the rights You grant and how the terms and conditions apply to You and the licensees of Your Modifications. Notwithstanding the foregoing, when You "stand in the shoes" of Yahoo!, You are not subject to the jurisdiction provision under Section 7, which requires all disputes under this Agreement to be subject to the jurisdiction of federal or state courts of northern California.
1.4 - For the Software or any Modification You distribute in compiled or object code format, You must also provide recipients with access to the Software or Modification in source code format along with a complete copy of this Agreement. The distribution of the Software or Modifications in compiled or object code format may be under a license of Your choice, provided that You are in compliance with the terms of this Agreement. In addition, You must make absolutely clear that any license terms applying to such Software or Modification that differ from this Agreement are offered by You alone and not by Yahoo!, and that such license does not restrict recipients from exercising rights in the source code to the Software granted by Yahoo! under this Agreement or rights in the source code to any Modification granted by You as described in Section 1.3.
1.5 - This Agreement does not limit Your right to distribute files that are entirely Your own work (i.e., which do not incorporate any portion of the Software and are not Modifications) under any terms You choose.
Support
Yahoo! has no obligation to provide technical support or updates to You. Nothing in this Agreement requires Yahoo! to enter into any license with You for any other edition of the Software.
Intellectual Property Rights
3.1 - Except for the license expressly granted under copyright in Section 1.1, no rights, licenses or forbearances are granted or may arise in relation to this Agreement whether expressly, by implication, exhaustion, estoppel or otherwise. All rights, including all intellectual property rights, that are not expressly granted under this Agreement are hereby reserved.
3.2 - In any copy of the Software or in any Modification you create, You must retain and reproduce, any and all copyright, patent, trademark, and attribution notices that are included in the Software in the same form as they appear in the Software. This includes the preservation of attribution notices in the form of trademarks or logos that exist within a user interface of the Software.
3.3 - This license does not grant You rights to use any party`s name, logo, or trademarks, except solely as necessary to comply with Section 3.2.
Disclaimer of Warranties
THE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTY OF ANY KIND. YAHOO! MAKES NO WARRANTIES, WHETHER EXPRESS, IMPLIED, OR STATUTORY REGARDING OR RELATING TO THE SOFTWARE. SPECIFICALLY, YAHOO! DOES NOT WARRANT THAT THE SOFTWARE WILL BE ERROR FREE OR WILL PERFORM IN AN UNINTERRUPTED MANNER. TO THE GREATEST EXTENT ALLOWED BY LAW, YAHOO! SPECIFICALLY DISCLAIMS ALL IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE (EVEN IF YAHOO! HAD BEEN INFORMED OF SUCH PURPOSE), AND NONINFRINGEMENT WITH RESPECT TO THE SOFTWARE, ANY MODIFICATIONS THERETO AND WITH RESPECT TO THE USE OF THE FOREGOING.
Limitation of Liability
IN NO EVENT WILL YAHOO! BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING WITHOUT LIMITATION LOSS OF PROFITS, LOSS OF USE, BUSINESS INTERRUPTION, LOSS OF DATA, COST OF COVER) IN CONNECTION WITH OR ARISING OUT OF OR RELATING TO THE FURNISHING, PERFORMANCE OR USE OF THE SOFTWARE OR ANY OTHER RIGHTS GRANTED HEREUNDER, WHETHER ALLEGED AS A BREACH OF CONTRACT OR TORTIOUS CONDUCT, INCLUDING NEGLIGENCE, AND EVEN IF YAHOO! HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Term and Termination
6.1 - This Agreement will continue in effect unless and until terminated earlier pursuant to this Section 6.
6.2 - In the event You violate the terms of this Agreement, Yahoo! may terminate this Agreement.
6.3 - All licenses granted hereunder shall terminate upon the termination of this Agreement. Termination will be in addition to any rights and remedies available to Yahoo! at law or equity or under this Agreement.
6.4 - Termination of this Agreement will not affect the provisions regarding reservation of rights (Section 3.1), provisions disclaiming or limiting Yahoo!`s liability (Sections 4 and 5), Termination (Section 6) or Miscellaneous (Section 7), which provisions will survive termination of this Agreement.
Miscellaneous
This Agreement contains the entire agreement of the parties with respect to the subject matter of this Agreement and supersedes all previous communications, representations, understandings and agreements, either oral or written, between the parties with respect to said subject matter. The relationship of the parties hereunder is that of independent contractors, and this Agreement will not be construed as creating an agency, partnership, joint venture or any other form of legal association between the parties. If any term, condition, or provision in this Agreement is found to be invalid, unlawful or unenforceable to any extent, this Agreement will be construed in a manner that most closely effectuates the intent of this Agreement. Such invalid term, condition or provision will be severed from the remaining terms, conditions and provisions, which will continue to be valid and enforceable to the fullest extent permitted by law. This Agreement will be interpreted and construed in accordance with the laws of the State of California and the United States of America, without regard to conflict of law principles. The U.N. Convention on Contracts for the International Sale of Goods shall not apply to this Agreement. All disputes arising out of this Agreement involving Yahoo! or any of its subsidiaries shall be subject to the jurisdiction of the federal or state courts of northern California, with venue lying in Santa Clara County, California. No rights may be assigned, no obligations may be delegated, and this Agreement may not be transferred by You, in whole or in part, whether voluntary or by operation of law, including by way of sale of assets, merger or consolidation, without the prior written consent of Yahoo!, and any purported assignment, delegation or transfer without such consent shall be void ab initio. Any waiver of the provisions of this Agreement or of a party`s rights or remedies under this Agreement must be in writing to be effective. Failure, neglect or delay by a party to enforce the provisions of this Agreement or its rights or remedies at any time, will not be construed or be deemed to be a waiver of such party`s rights under this Agreement and will not in any way affect the validity of the whole or any part of this Agreement or prejudice such party`s right to take subsequent action.