| 1 |
One of the approaches could be to use xmlrpc for the establishment of |
| 2 |
jobs at the server. Other than this a log mentioning the complete |
| 3 |
build of the final image will be useful so as to avoid the repetition |
| 4 |
of the entire process in case some one wants to build a similar image |
| 5 |
they built earlier. |
| 6 |
|
| 7 |
On Fri, Mar 13, 2009 at 2:46 AM, Ned Ludd <solar@g.o> wrote: |
| 8 |
> On Fri, 2009-03-13 at 01:40 +0530, kartik rustagi wrote: |
| 9 |
>> > Did you delete it from the wiki, then? Or should I? |
| 10 |
>> I have deleted it. |
| 11 |
>> |
| 12 |
>> Their is one another idea listed at the wiki about Creating a Web |
| 13 |
>> based image builder for Gentoo similar to SUSE studio. I discussed |
| 14 |
>> this with some people and they find it to be interesting and useful to |
| 15 |
>> increase Gentoo's adopt-ability further. The back end can be done |
| 16 |
>> mostly in Python and thus suits my skill set. The backend with quite a |
| 17 |
>> lot of functionalities plus a basic front end might be just |
| 18 |
>> appropriate for the time span of Gsoc. |
| 19 |
>> |
| 20 |
>> Request for comments .... |
| 21 |
>> |
| 22 |
>> Regards |
| 23 |
>> Kartik Rustagi |
| 24 |
> |
| 25 |
> Backend being in python would be fine. Frontend should work more or less something like this mock up. |
| 26 |
> |
| 27 |
> http://tinderbox.dev.gentoo.org/image/ |
| 28 |
> |
| 29 |
> Note these are binary feeds of packages that have already been built and |
| 30 |
> not a frontend to run some random emerge for pkgs. However for pkgs that |
| 31 |
> don't exist. We probably would want to make some sort of log so that we |
| 32 |
> know which types of package jobs to dispatch to the misc bin builders |
| 33 |
> that are out there now. |
| 34 |
> |
| 35 |
> -- |
| 36 |
> Ned Ludd <solar@g.o> |
| 37 |
> Gentoo Linux |
| 38 |
> |
| 39 |
> |
Archives