[sugar] Mandatory Changelogs
Mon Oct 29 14:17:57 EDT 2007
Thanks for your question. The short answer is that Koji and the
dropboxes are completely independent, parallel mechanisms for creating
binary RPM repositories to be composed by pilgrim into a build image.
Today, ChangeLogs are required only for packages included by the dropbox
mechanism. We are in discussions with folks who are knowledgable about
Koji (namely Dave Woodhouse and Dennis Gilmore) to produce a wrapper for
the Koji tag command that will record similar information. In the
meantime, writing detailed RPM changelogs that describe the purpose of
introducing the new package (in addition to any packaging changes) would
be enourmously useful.
Checking the source:
shows that Joyride is indeed configured to pull packages from the OLPC-2
On Mon, Oct 29, 2007 at 10:20:22AM +0000, Simon McVittie wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On Sat, 27 Oct 2007 at 18:55:34 -0400, Michael Stone wrote:
> > Dear Sugar and Devel,
> > ChangeLogs in the format described on
> > http://wiki.laptop.org/go/Build_system#ChangeLog_Format
> > are now MANDATORY for package inclusion. Please write yours.
> How does this work for Koji users? I build the OLPC Telepathy components
> for what-was-FRS-last-time-I-looked in the OLPC-2 stream in Koji.
> Will they be integrated into Joyride automatically, or do I have to download
> the RPMs (assuming that's even possible) and re-upload them via my public_rpms?
> If they're integrated automatically, how and where do I write
> changelogs? I'm happy to write the RPM %changelog in the desired format
> if that's what you want...
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: OpenPGP key: http://www.pseudorandom.co.uk/2003/contact/ or pgp.net
> -----END PGP SIGNATURE-----
> Devel mailing list
> Devel at lists.laptop.org
More information about the Sugar-devel