Date: Fri, 14 May 2010 01:17:31 +0100
From: Graham Cobb<[email protected]>
To: [email protected]
Subject: Re: [MeeGo-dev] how to start developing on MeeGo?
Message-ID:<[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
On Friday 30 April 2010 16:38:05 Graham Cobb wrote:
On Wednesday 28 April 2010 22:12:07 David Greaves wrote:
Well, the build systems team inside Nokia has begun writing some docs to
assist internal developers with much the same issues. We're starting to
publish some of them. A first page came out today
http://wiki.meego.com/Packaging/Deb_conversion_example
Thanks. I have been reading some tutorials as well as the Fedora
documentation (which is not as complete as I would like). And this page is
certainly useful.
I have managed to create (and install) my first rpm but I have a few
questions which I haven't found answers to yet:
I have now managed to create my first rpms using a chroot, and I have the
first steps towards creating automated overnight builds like I have for
Maemo.
In order to do automated builds, I have patched mic-chroot to allow me to
specify the command line that will be executed in the chroot. I have created
a bug report (2098) with my patch for consideration for adding into
mic-chroot.
I am curious for the same question too. How do you guys automatically
run something under mic-chroot (without the console)? This is necessary
for the nightly build script.
Here is my way,
1) run mic-chroot to start the MeeGo chroot jail so all directories are
mounted
2) run "chroot --userspec=meego:meego $CHROOT_DIR bash -c ..."
If Graham's patch is accept by MeeGo, I like to start to use it too.
Regards,
Dengyi
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
