Hi Pascal, Am Wednesday 03 May 2006 12:32 schrieb Pascal Bleser:

Are there any guidelines on how to submit something into the Build Service ?

opensuse-buildservice ml is maybe a better place

I installed Peter's osc, which seems by far the most practical and comfortable way to use the Build Service (I mean, the web interface is "pretty" but useless IMO, at least to me - I want to script, automate, work on the shell, not click around in the browser).

Garret is here this week and we work on a new Web interface JFYI-

Now, when I "osc ls", I see various subdirs, like home:cihlarov playground_abauer Debian-etch AdriansPlayground qsvn Kopete packman SL10.0 Amarok_Devel etc...

Those are all very different in structure and purpose.

Is there any guideline on how to submit a project ? e.g. make it a toplevel (e.g. qsvn), have your own namespace (e.g. guru/amarok), ... ?

We think that by default everthing should be below the home: namespace. We can make the projects more official by moving it to a different namespace. A guru or KDE or ... namespace for certain groups would be possible as well.

Seems to me there isn't any as of now, which already causes chaos in the repository structure now, AFAICS ;)

yes, we need to clean this up, before we make the BS real public ...

BTW, I'm already maintaining the latest amarok releases in my package repository. Let's pick that one as an example. How are we supposed to work together, to avoid duplicate efforts ? Or is it way too early to even consider it ? ;)

There are two cases. You can either get direct write access to the project, by the project owner. You can also create "a linked package with patch" to suggest a change. The tools will make this hopefully very easy. We have already the first version of package linking support in the Web interface. Such a modification can be linked easily later by the original project owner. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de