No idea at all, sorry.
But in the core, the build process is the same, whatever you use on top
of the debian packaging system to automate the build process of several
packages.
Debian has tools for that kind of automation, too. See pbuilder [1], for
example.
Regards,
Jussi
[1]
http://www.netfort.gr.jp/~dancer/software/pbuilder-doc/pbuilder-doc.html#introduction
Trilok Soni wrote:
Hi Jussi,
On Jan 9, 2008 3:28 PM, Jussi Hakala <[EMAIL PROTECTED]> wrote:
Trilok Soni wrote:
Thanx Jussi for the above explanation of crocodile based scripts. I
was looking for
such script which can build debian source packages, particularly maemo
chinook repository
source packages automatically.
Crocodile can be used for this, I've myself built several maemo packages
using crocodile.
Do you suggest crocodile is good fit for such tasks? OR do I have
independently fetch each source pacakge
and run dpkg-buildpacakge in the order of dependencies - this would be
very hectic I would say.
I don't think Nokia is using crocodile internally, they have their own
system. But the packages are nevertheless compiled inside scratchbox
with maemo's toolchain and their combination of devkits selected for the
target.
So, even using apt-get source and dpkg-buildpackage manually, you should
end up with properly built packages. If you want to avoid manual work,
you can use crocodile :)
I'd suggest removing files from the patches and the variables
subdirectories in crocodile to avoid applying the debian patches in the
build process, maemo packages don't need them.
Thanx for the inputs. I will try now to build these maemo packages
using crocodile.
Do you think anytime Nokia opening up these internal scripts? OR should I ask
these on the maemo-developers ML?
_______________________________________________
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
