[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-active
Subject:    Re: git repo for kickstarts
From:       martin brook <martin.brook100 () googlemail ! com>
Date:       2012-04-24 9:05:10
Message-ID: CA+uP_P7wFv3dz4hEGT9+iAoNkEODf5dvCqyNygGTqDParO7cyg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Marco Hi,

The kickstarts can be made using the kickstarter tool from yaml
descriptions so it may be possible to have common parts which would include
the lists of Plasma Active packages and device specific parts.

At least for Mer see  http://wiki.merproject.org/wiki/Kickstarter

BR

vgrade


On Tue, Apr 24, 2012 at 9:46 AM, Marco Martin <notmart@gmail.com> wrote:

> Hi all,
>
> this is mostly for an opinion, still didn't do any of this...
> right now to build meego and mer images we have several kickstart files
> spreaded around, for different devices and for different repositories
> (devel,
> testing, releases)
>
> I think they should be in a git repository, with files always updated to
> the
> last officially built image, there are several options how to manage the
> files:
> * each combo repo version/device would be a different file, so there would
> be
> mer-x86-testing.ks meego-x86-devel.ks mer-archos-devel.ks etc
> * each device has a different file, but testing and devel version are
> branches
> of the git repo
> * each testing/devel version is a different file, but different devices are
> branches
>
> I'm kinda leaning for option 2, but even without using branches at all
> would
> be less mess than now.
> opinions? comments?
>
> --
> Marco Martin
> _______________________________________________
> Active mailing list
> Active@kde.org
> https://mail.kde.org/mailman/listinfo/active
>

[Attachment #5 (text/html)]

<div class="gmail_extra">Marco Hi,</div><div class="gmail_extra"><br></div><div \
class="gmail_extra">The kickstarts can be made using the kickstarter tool from yaml \
descriptions so it may be possible to have common parts which would include the lists \
of Plasma Active packages and device specific parts.</div> <div \
class="gmail_extra"><br></div><div class="gmail_extra">At least for Mer see  <a \
href="http://wiki.merproject.org/wiki/Kickstarter">http://wiki.merproject.org/wiki/Kickstarter</a> \
</div><div class="gmail_extra"><br></div><div class="gmail_extra">BR</div><div \
class="gmail_extra"><br></div><div class="gmail_extra"> vgrade</div><div \
class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 24, 2012 at 9:46 AM, \
Marco Martin <span dir="ltr">&lt;<a href="mailto:notmart@gmail.com" \
target="_blank">notmart@gmail.com</a>&gt;</span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Hi all,<br> <br>
this is mostly for an opinion, still didn&#39;t do any of this...<br>
right now to build meego and mer images we have several kickstart files<br>
spreaded around, for different devices and for different repositories (devel,<br>
testing, releases)<br>
<br>
I think they should be in a git repository, with files always updated to the<br>
last officially built image, there are several options how to manage the<br>
files:<br>
* each combo repo version/device would be a different file, so there would be<br>
mer-x86-testing.ks meego-x86-devel.ks mer-archos-devel.ks etc<br>
* each device has a different file, but testing and devel version are branches<br>
of the git repo<br>
* each testing/devel version is a different file, but different devices are<br>
branches<br>
<br>
I&#39;m kinda leaning for option 2, but even without using branches at all would<br>
be less mess than now.<br>
opinions? comments?<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Marco Martin<br>
_______________________________________________<br>
Active mailing list<br>
<a href="mailto:Active@kde.org">Active@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/active" \
target="_blank">https://mail.kde.org/mailman/listinfo/active</a><br> \
</font></span></blockquote></div><br></div>



_______________________________________________
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active


[prev in list] [next in list] [prev in thread] [next in thread]