"Andrew Flegg" <[EMAIL PROTECTED]> writes:
> 1) Simple ability to upload a source package(s).
> 2) Have that source package compiled on as many SDKs as possible (OS 2006, OS
> 2007 and OS 2008 should be possible with some/most packages).
> 3) The ability to update a source package in a simple manner (triggering a
> recompile).
> 4) When a new SDK is released, everything should be recompiled and redeployed
> to extras-{devel,testing,...}.
These are the main points for me too, but in addition:
5) Subject to some automated measure of quality (maybe just successful
building), the built packages are automatically published into the
extras{-testing} repository.
6) If it doesn't already exist, an entry in the Application Catalog is
automatically created, including .install file(s) for all supported
OSs.
Then there are (probably obvious) things about the detailed operation
of the above points, like automatically emailing the uploader if a
package doesn't build.
If possible, it might make sense for the interface to the auto-builder
to be integrated into garage.
- It feels reasonable to say that a project must have a garage page,
in order to use the auto-builder.
- Instead of emailing the uploaded in case of build failure, the
auto-builder could submit a bug to the project's tracker instead.
- Garage could provide a convenience page for uploading a source
package to the auto-builder. For the benefit of people with lots of
projects, however, this probably should not be the _only_ uploading
interface; it would be necessary if something scriptable worked
also.
Regards,
Neil
_______________________________________________
maemo-developers mailing list
[email protected]
https://lists.maemo.org/mailman/listinfo/maemo-developers
