git repo for kickstarts
martin brook
martin.brook100 at googlemail.com
Tue Apr 24 09:05:10 UTC 2012
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 at 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 at kde.org
> https://mail.kde.org/mailman/listinfo/active
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/active/attachments/20120424/ce3773d9/attachment.html>
More information about the Active
mailing list