aboutsummaryrefslogtreecommitdiffstats
path: root/meta-gpe
AgeCommit message (Expand)Author
2017-04-05recipes: add removal date to PNBLACKLIST messagesMartin Jansa
2017-02-13recipes: blacklist recipes depending on blacklisted recipesMartin Jansa
2017-02-13python-edbus exquisite elementary libeweather unionfs-fuse xfsprogs gmtk devi...Martin Jansa
2016-09-05gtk-doc: disable where necessaryAlexander Kanavin
2016-08-22meta-oe: remove trailing spacesMartin Jansa
2016-06-15fbreader: fix return code issue on gcc6Derek Straka
2016-06-13abiword, fbreader, tvheadend, glmark2, libqmi, modemmanager, thrift, wvdial, ...Martin Jansa
2016-05-06fbreader: add cflags fix for fribidi 0.19.7Derek Straka
2014-11-28meta-gpe: Add LAYERVERSION and LAYERDEPENDSJackie Huang
2014-07-15meta-gpe: use BPN in SRC_URIRobert Yang
2014-06-21recipes: add missing pkgconfig class inheritsRichard Purdie
2014-03-05recipes: bump PRs and remove PRINCsMartin Jansa
2014-02-23recipes: convert remaining SUMMARY/DESCRIPTION cosmetic issuesMatthieu CRAPET
2013-11-01recipes: Remove PR = r0 from all recipesMartin Jansa
2013-08-14fbreader: add sqlite3 dependencyMartin Jansa
2013-05-03README: show github mirror URL in layer dependenciesMartin Jansa
2013-04-26README: add -M to git send-email exampleMartin Jansa
2013-04-26README: add me to maintainers in some layersMartin Jansa
2013-04-15recipes: Unify indentationMartin Jansa
2013-04-15libgpewidget: fix warning about overwritting keysMartin Jansa
2012-12-04fbreader: move to meta-gpe due to libgpewidget dependencyMarcin Juszkiewicz
2012-09-20recipes: bump PR to rebuild after libffi5 -> libffi6Martin Jansa
2012-07-24libgpewidget: cleanup thanks to new gtk-doc.bbclassMartin Jansa
2012-05-06gpe-scap: migrate to use libsoup-2.4 instead of libsoup-2.2 APIMartin Jansa
2012-05-04libgpewidget: fix build with glib-2.32Martin Jansa
2012-04-26README: keep PATCH prefix in subject-prefix, some people filter their inbox b...Martin Jansa
2012-04-19README: fix meta-efl, meta-gpe and meta-xfce to point to openembedded.orgDenys Dmytriyenko
2012-02-13recipes: bump PR to rebuild .la files without libz.laMartin Jansa
2012-02-01minilite: import from OE classicKoen Kooi
2011-07-14Drop PRIORITY variablePaul Eggleton
2011-05-23gpe-scap: import from OE rev aae5b51e4a8dd57b28a6f91e6c14a5311aadbdaeKoen Kooi
2011-05-09conf/layer.conf: Use .= for BBPATH and += for BBFILESKhem Raj
2011-04-18libgpe-widget: import from OE .dev a263524ca222f1968507489313211b4fa674e963Koen Kooi
2011-04-18meta-gpe: add layerKoen Kooi
option> OpenEmbedded Core user contribution treesGrokmirror user
summaryrefslogtreecommitdiffstats
path: root/meta/files/common-licenses/BSD
blob: c7a0aa4f9417238fe9b9c6d1404f10180a80a5e6 (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
Copyright (c) The Regents of the University of California.
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
   notice, this list of conditions and the following disclaimer in the
   documentation and/or other materials provided with the distribution.
3. Neither the name of the University nor the names of its contributors
   may be used to endorse or promote products derived from this software
   without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.