<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/recipes-extended/sed, branch pyro-nfvaccess</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=pyro-nfvaccess</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=pyro-nfvaccess'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2017-03-07T20:05:31+00:00</updated>
<entry>
<title>recipes: Move out stale GPLv2 versions to a seperate layer</title>
<updated>2017-03-07T20:05:31+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2017-03-02T12:04:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2345af9b4829ed3eed5abf60f2483055649f8af7'/>
<id>urn:sha1:2345af9b4829ed3eed5abf60f2483055649f8af7</id>
<content type='text'>
These are recipes where the upstream has moved to GPLv3 and these old
versions are the last ones under the GPLv2 license.

There are several reasons for making this move. There is a different
quality of service with these recipes in that they don't get security
fixes and upstream no longer care about them, in fact they're actively
hostile against people using old versions. The recipes tend to need a
different kind of maintenance to work with changes in the wider ecosystem
and there needs to be isolation between changes made in the v3 versions
and those in the v2 versions.

There are probably better ways to handle a "non-GPLv3" system but right
now having these in OE-Core makes them look like a first class citizen
when I believe they have potential for a variety of undesireable issues.

Moving them into a separate layer makes their different needs clearer, it
also makes it clear how many of these there are. Some are probably not
needed (e.g. mc), I also wonder whether some are useful (e.g. gmp)
since most things that use them are GPLv3 only already. Someone could
now more clearly see how to streamline the list of recipes here.

I'm proposing we mmove to this separate layer for 2.3 with its future
maintinership and testing to be determined in 2.4 and beyond.

(From OE-Core rev: 19b7e950346fb1dde6505c45236eba6cd9b33b4b)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>quilt/acl/attc/sed: Fix use of tar's --exclude option for tar &gt;= 1.29</title>
<updated>2016-08-10T09:46:31+00:00</updated>
<author>
<name>Mariano Lopez</name>
<email>mariano.lopez@linux.intel.com</email>
</author>
<published>2016-08-05T11:25:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=262c81e3ca2583be2d44b7195747f1a42a10a9f3'/>
<id>urn:sha1:262c81e3ca2583be2d44b7195747f1a42a10a9f3</id>
<content type='text'>
Starting from tar 1.29 the --exclude option won't work
anymore if is not used before the path. There are some
recipes that copy the ptest using tar and --exclude
option. This fixes these for OE-Core recipes.

[YOCTO #9763]

(From OE-Core rev: 2ba55933c81f78f4e4c36e21c59e935f74ce0f52)

Signed-off-by: Mariano Lopez &lt;mariano.lopez@linux.intel.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta: update patch metadata</title>
<updated>2016-07-08T08:57:24+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@intel.com</email>
</author>
<published>2016-06-27T19:59:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e49d337e848a2cf72045e492c20482336b929381'/>
<id>urn:sha1:e49d337e848a2cf72045e492c20482336b929381</id>
<content type='text'>
Enforce the correct tag names across all of oe-core for consistency.

(From OE-Core rev: 606a43dc38a00cc243f933722db657aea4129f8e)

Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta: Fix Upstream-Status statements</title>
<updated>2015-09-12T22:01:53+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@intel.com</email>
</author>
<published>2015-09-10T18:59:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1c914a844b35ff57b1c528251a9eaa19cedbaa10'/>
<id>urn:sha1:1c914a844b35ff57b1c528251a9eaa19cedbaa10</id>
<content type='text'>
Fix a variety of problems such as typos, bad punctuations, or incorrect
Upstream-Status values.

(From OE-Core rev: bd220fe6ce8c3a0805f13a14706d3130ea872604)

Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>sed: Make locale depenencies glibc specific</title>
<updated>2015-07-27T11:28:00+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2015-07-25T13:45:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=898fd07d7754f96432338e7a2989b0de17db8be3'/>
<id>urn:sha1:898fd07d7754f96432338e7a2989b0de17db8be3</id>
<content type='text'>
Only glibc provides this base locale so make the dependency glibc
specific to avoid build failures with other libcs.

(From OE-Core rev: 359b756b87abc3fed1d2ef4840ba01bb0c23f368)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>sed: rrec on locale-base-ru-ru, not rdep</title>
<updated>2015-07-25T13:41:42+00:00</updated>
<author>
<name>Abdur Rehman</name>
<email>abdur_rehman@mentor.com</email>
</author>
<published>2015-07-23T15:20:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=98b5364baea1da08ded1e5b9b2fb553ec34322d3'/>
<id>urn:sha1:98b5364baea1da08ded1e5b9b2fb553ec34322d3</id>
<content type='text'>
This locale package isn't guaranteed to exist, depending on the value of
GLIBC_GENERATE_LOCALES.

The value of GLIBC_GENERATE_LOCALES can be specified to not contain
locale-base-ru-ru, thus resulting in unsatisfied dependency. Its better
to remove hardcoded dependency upon locale-base-ru-ru in favor of a
recommendation, as this locale isn't always available depending upon the
value of GLIBC_GENERATE_LOCALES.

(From OE-Core rev: f9ec9c89956810f21955819677e92588540a4748)

Signed-off-by: Christopher Larson &lt;chris_larson@mentor.com&gt;
Signed-off-by: Abdur Rehman &lt;abdur_rehman@mentor.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>recipes: Fix charset.alias for musl</title>
<updated>2015-04-21T06:20:25+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2015-04-16T02:00:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=72830226190b828854e3d27720711f9c147bfe28'/>
<id>urn:sha1:72830226190b828854e3d27720711f9c147bfe28</id>
<content type='text'>
This is same gnulib fix replicated across needed recipes

Change-Id: I756713407111a726eae98e26c9c1ff64981371c0
(From OE-Core rev: fbe6d2c12aa9f7956bc87efeb68cb64b26b60c7a)

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>sed: Cope with ${bindir} and ${base_bindir} being the same</title>
<updated>2015-03-10T10:47:43+00:00</updated>
<author>
<name>Mike Crowe</name>
<email>mac@mcrowe.com</email>
</author>
<published>2015-02-05T17:50:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=3f8ce1e755e4204c7bf03f937d063b70abd8c73c'/>
<id>urn:sha1:3f8ce1e755e4204c7bf03f937d063b70abd8c73c</id>
<content type='text'>
${bindir} and ${base_bindir} may be the same. If they are don't try and
move files onto themselves.

(From OE-Core rev: ab1452cacce6584bab27b73fc1e22d603606ecda)

Signed-off-by: Mike Crowe &lt;mac@mcrowe.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>sed-native: drop</title>
<updated>2015-02-02T12:41:12+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2015-01-29T13:24:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4213ccc7330523708d36b8143692f09757048b0d'/>
<id>urn:sha1:4213ccc7330523708d36b8143692f09757048b0d</id>
<content type='text'>
This was added back in the depths of history (around 2006 in OE-Classic)
when apparently the host sed couldn't always be relied upon. We now call
the host sed all over the place without this dependency and don't have
any problems. On the other hand, having it around can lead to races
where we're calling sed in one task and staging it to the sysroot in
another, the result being nasty failures compiling binutils for example.
Since it isn't needed, let's just drop it completely.

Fixes [YOCTO #7264].

(From OE-Core rev: 863a3966e1a200e7a15fbdbb8e04dce6e3f6c1a2)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>sed: add sed to RDEPENDS sed-ptest</title>
<updated>2014-08-28T14:12:44+00:00</updated>
<author>
<name>Robert Yang</name>
<email>liezhi.yang@windriver.com</email>
</author>
<published>2014-08-27T15:57:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b2dab1f6b0a0936c9a8136896544a684fedcbb25'/>
<id>urn:sha1:b2dab1f6b0a0936c9a8136896544a684fedcbb25</id>
<content type='text'>
Its test scripts require /bin/sed.

(From OE-Core rev: f1a3f28c3f2aa9f16c138712fbfd671d731fd62e)

Signed-off-by: Robert Yang &lt;liezhi.yang@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
