Gonna post this here if its alright with everybody (gonna post it even if it isnt).
1: Cyclic deps: As it is a package can trigger its own build by being newer (but the buildservice wont and give a cyclic deps issue) in gnome there is some part where this can hardly be avoided, basicly package X shouldnt be able to trigger its own build. tricky part is that it also have to track what was rebuild following this and ignore those for further rebuild too.
2: rpm/source backend: More of a question here are those there to allow futur use of local buildservice and sync those back to main server or is that some intern way to specify where one build his stuff on the system? I was thinking of installing a buildservice here once i get my new box then gonna be able to see much more clearly what my client do, as well as being much more pratical to build my stuff, i could prolly get my head arround doing some syncing stuff myself, but would be much more easier if server did that already (would allow peter to put it into his cli client too).
3: Add ProjectAdmin status to creator of project instead of Mainteneer: Add the admin status (i was already making my client so multiple user type can exist), user creating a project should be marked as admin and be allowed to erase the project themself (don't beat me if it's already somewhere in some todo but see too many people asking in here please erase this and that).
4: Add a Contributor user type: Contributor should be allowed to edit a package in a project and only that package not whole project.
that would be it for now.
Am Monday 17 July 2006 08:52 schrieb Jonathan Arson:
Gonna post this here if its alright with everybody (gonna post it even if it isnt).
1: Cyclic deps: As it is a package can trigger its own build by being newer (but the buildservice wont and give a cyclic deps issue) in gnome there is some part where this can hardly be avoided, basicly package X shouldnt be able to trigger its own build. tricky part is that it also have to track what was rebuild following this and ignore those for further rebuild too.
Cyclics deps are in general in first place a broken software. However, we have to deal with them since quite some time, so we offer workarounds via the configuration to break dependendcies as part of the porject configuration.
2: rpm/source backend: More of a question here are those there to allow futur use of local buildservice and sync those back to main server or is that some intern way to specify where one build his stuff on the system? I was thinking of installing a buildservice here once i get my new box then gonna be able to see much more clearly what my client do, as well as being much more pratical to build my stuff, i could prolly get my head arround doing some syncing stuff myself, but would be much more easier if server did that already (would allow peter to put it into his cli client too).
This is not possible right now, because some parts of the build service are not open source yet. However, I am in good hope to have this changed until the end of the year :)
3: Add ProjectAdmin status to creator of project instead of Mainteneer: Add the admin status (i was already making my client so multiple user type can exist), user creating a project should be marked as admin and be allowed to erase the project themself (don't beat me if it's already somewhere in some todo but see too many people asking in here please erase this and that).
IIRC we planned to use Maintainer and Contributor to have this seperation.
4: Add a Contributor user type: Contributor should be allowed to edit a package in a project and only that package not whole project.
that would be it for now.
On Mon, Jul 17, 2006 at 02:52:59AM -0400, Jonathan Arson wrote:
Gonna post this here if its alright with everybody (gonna post it even if it isnt).
1: Cyclic deps: As it is a package can trigger its own build by being newer (but the buildservice wont and give a cyclic deps issue) in gnome there is some part where this can hardly be avoided, basicly package X shouldnt be able to trigger its own build. tricky part is that it also have to track what was rebuild following this and ignore those for further rebuild too.
Actually the build service just looks at source changes, so a package can't trigger its own build. Cyclic dependencies are a thing two avoid, as each package has to be built twice, but they don't kill the build service.
Cheers, Michael.
buildservice@lists.opensuse.org
-
Adrian Schröter -
Jonathan Arson -
Michael Schroeder