<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi all,<br>
<br>
On 14.01.2013 21:35, Marco Martin wrote:<br>
</div>
<blockquote cite="mid:201301142135.03244.notmart@gmail.com"
type="cite">
<pre wrap="">Hi all,
right now most of the images, x86 and some of the arm ones are created from a
series of kickstart files in the plasma-active-kickstart, legacy-kickstarts
subdirectory.
as the name "legacy" says, there are better ways to do that.
I recreated the info for creating images in the form of yaml files, still in
the plasma-active-kickstart repo.
That's for coherence with Nemo:
It has a general yaml file plus one yaml file for each hardware adaptation:
in this way it will be possible to produce a kickstart file for each device
with a single command, you can try it with:
mer-kickstarter -e . -c latest-devel/plasma-active-latest-devel.yaml -o
active-latest-ks/
as a bonus it uses now all yaml adaptation files from Nemo, gaining support
for n900,950,pandaboard and an image optimized for virtual machines (with
virtualbox tools and stuff)
Since we have now contributions of adaptations to new devices such as the
nexus7, it would be cool if everything will go there, so will be possible to
better track what are all the devices where active works, and make easier for
people to contribute and build images themselves.
It's still not perfect, but i would like to switch the weekly devel images to
this asap.</pre>
</blockquote>
<br>
I integrated the legacy kickstart files of Archos gen9 and Nexus7
into<br>
yaml structure of plasma-active-kickstart maintaining repository.
Also<br>
I added the repo definitions of testing based images, which are
still<br>
using the frozen Mer core '0.20120816.1' dependencies.<br>
<br>
The ce/nemo community is building against the always latest mer
release<br>
but we are building on top of a older fixed one for <b>testing</b>.
This will hit us<br>
at some point for adaptations we are not building on our own. We
should<br>
ask the nemo maintainers to offer us package repositories which are<br>
based on the same fixed mer core release. As short term work-around<br>
I just copied over breaking packages and rebuild them our<br>
Project:KDE:Mer_Extras:Adaptation:Tegra3:Nexus7 project on<br>
build.pub.meego.com<br>
<br>
Affected repositories are:<br>
- ce-adaptation-n900 (<a class="moz-txt-link-freetext" href="http://repo.pub.meego.com">http://repo.pub.meego.com</a>)<br>
- ce-adaptation-n9xx-common (<a class="moz-txt-link-freetext" href="http://repo.pub.meego.com">http://repo.pub.meego.com</a>)<br>
- ce-adaptation-n950-n9 (<a class="moz-txt-link-freetext" href="http://repo.pub.meego.com">http://repo.pub.meego.com</a>)<br>
- ce-adaptation-pandaboard (<a class="moz-txt-link-freetext" href="http://repo.pub.meego.com">http://repo.pub.meego.com</a>)<br>
- nemo-hw-nv-tegra3-common (<a class="moz-txt-link-freetext" href="http://repo.merproject.org">http://repo.merproject.org</a>)<br>
- nemo-hw-nv-tegra3-nexus7 (<a class="moz-txt-link-freetext" href="http://repo.merproject.org">http://repo.merproject.org</a>)<br>
<br>
git clone git://anongit.kde.org/plasma-active-kickstart<br>
<br>
Please note,by the integration work several packages got dropped
from<br>
the Archos and Nexus arm based kickstart files. I fear we have to re<br>
added some of them again into a e.g. generic/plasma-active-arm.yaml<br>
file or (what I prefer) adding the lost packages to the
'plasma-active'<br>
meta packages of devel and testing project. Here a short overview<br>
of dropped packages from arm based ks files:<br>
<br>
Nexus 7:<br>
libqtdeclarative4-particles, less, tar, upower, strace and several
games.<br>
<br>
Archos Gen9:<br>
alsa-plugins-pulseaudio, libqtdeclarative4-particles, less, tar,
upower, <br>
strace and several games.<br>
<br>
If you like to try out or take a deep look: <a class="moz-txt-link-freetext" href="ftp://5.9.162.110">ftp://5.9.162.110</a><br>
<br>
Yes the Archos Gen9 devel images are still broken, but from now on
we<br>
can think about how to fix it.<br>
<br>
Cheers,<br>
<br>
Maurice<br>
</body>
</html>