<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-openembedded.git/meta-webserver/recipes-webadmin, branch daisy</title>
<subtitle>Mirror of git.openembedded.org/meta-openembedded</subtitle>
<id>https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=daisy</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=daisy'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/'/>
<updated>2014-01-10T11:20:18+00:00</updated>
<entry>
<title>ajenti: remove</title>
<updated>2014-01-10T11:20:18+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2014-01-03T13:58:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=c9236a3665494fb53f8ab46cdf51007bebde7f3e'/>
<id>urn:sha1:c9236a3665494fb53f8ab46cdf51007bebde7f3e</id>
<content type='text'>
In recent versions, upstream has decided to place additional
restrictions on commercial use beyond a standard open source license
(LGPLv3) [1]. This makes it hard to set a LICENSE value that is easily
understood. Of course, as the authors, they have the right to decide
what licensing terms they wish to distribute their project under, and we
could always set LICENSE_FLAGS to denote the extra terms, but this is
somewhat messy and personally I feel less inclined to continue
maintaining this recipe in meta-webserver now, especially since I
originally put it together on my own time. At the moment due to a
branch/commit mismatch it is no longer fetching in any case.

(If someone wants to resurrect this recipe in another layer, they are
more than welcome to do so.)

[1] http://support.ajenti.org/topic/351265-clarify-licensing/

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>webmin: add from meta-baryon</title>
<updated>2013-07-31T16:41:21+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2013-07-13T15:07:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=246bedc1c6b3e2830ca0a8fae8c30b8624f46ab2'/>
<id>urn:sha1:246bedc1c6b3e2830ca0a8fae8c30b8624f46ab2</id>
<content type='text'>
No changes.

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>recipes: Unify indentation</title>
<updated>2013-04-15T14:23:17+00:00</updated>
<author>
<name>Martin Jansa</name>
<email>Martin.Jansa@gmail.com</email>
</author>
<published>2013-04-13T20:49:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=a45830a39bb47a9eab27980d52966226c9504ea4'/>
<id>urn:sha1:a45830a39bb47a9eab27980d52966226c9504ea4</id>
<content type='text'>
* This change is only aesthetic (unlike indentation in Python
  tasks).
* Some recipes were using tabs.
* Some were using 8 spaces.
* Some were using mix or different number of spaces.
* Make them consistently use 4 spaces everywhere.
* Yocto styleguide advises to use tabs (but the only reason to keep
  tabs is the need to update a lot of recipes). Lately this advice
  was also merged into the styleguide on the OE wiki.
* Using 4 spaces in both types of tasks is better because it's less
  error prone when someone is not sure if e.g.
  do_generate_toolchain_file() is Python or shell task and also allows
  to highlight every tab used in .bb, .inc, .bbappend, .bbclass as
  potentially bad (shouldn't be used for indenting of multiline
  variable assignments and cannot be used for Python tasks).
* Don't indent closing quote on multiline variables
  we're quite inconsistent wheater it's first character on line
  under opening quote or under first non-whitespace character in
  previous line.

Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
Acked-by: Koen Kooi &lt;koen@dominion.thruhere.net&gt;
</content>
</entry>
<entry>
<title>ajenti: add new recipe</title>
<updated>2013-02-18T09:28:26+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2013-02-11T10:16:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=dbb905c9786eb4686ebc85d8e5aad1f481591448'/>
<id>urn:sha1:dbb905c9786eb4686ebc85d8e5aad1f481591448</id>
<content type='text'>
Add new recipe for the Ajenti web administration interface.

This was developed and tested with assistance from
Kevin Strasser &lt;kevin.strasser@linux.intel.com&gt;

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
</content>
</entry>
</feed>
