[opensuse-buildservice] [RFC] General use of enable/disable flags.
General use of enable/disable flags
=====================================
1. Current state
==================
Currently the enable/disable tags only influence the build handling.
XML wise they are direct children of the <package> element.
The schema for enable/disable tags currently is:
[[[
Marcus Rueckert wrote:
2. Planned changes ====================
There are more flags, which should be configurable by the user:
* build Will this package be build? * publish Will the package synced out? * debuginfo Will the buildservice automatically generate debuginfo package? * usedforbuild Will the package be used for building other package in the same project? * more?
I have an idea, but I don't know whether it's desirable and doable :) What about: a) per-subpackage flags? b) "mirror" flag? That is, make the (sub)package available at software.o.o/download, but don't push it to mirrors (eg. mirroring of debuginfos could perhaps generate more traffic that direct download by a few users). Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2007-03-15 16:00:26 +0100, Michal Marek wrote:
I have an idea, but I don't know whether it's desirable and doable :)
What about: a) per-subpackage flags?
use case?
b) "mirror" flag? That is, make the (sub)package available at software.o.o/download, but don't push it to mirrors (eg. mirroring of debuginfos could perhaps generate more traffic that direct download by a few users).
we plan to use a special debuginfo tree here. similar to what we do for factory. so the mirror admin can decide if they want to pull the debuginfo tree too. maybe that covers your subpackage flags part too? darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Marcus Rueckert wrote:
b) "mirror" flag? That is, make the (sub)package available at software.o.o/download, but don't push it to mirrors (eg. mirroring of debuginfos could perhaps generate more traffic that direct download by a few users).
we plan to use a special debuginfo tree here. similar to what we do for factory. so the mirror admin can decide if they want to pull the debuginfo tree too. maybe that covers your subpackage flags part too?
Yeah this would be a better (not overdesigned) approach :) Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Mar 14, 2007 at 06:57:40PM +0100, Marcus Rueckert wrote: [...]
2. Planned changes ====================
There are more flags, which should be configurable by the user:
* build Will this package be build? * publish Will the package synced out? * debuginfo Will the buildservice automatically generate debuginfo package? * usedforbuild Will the package be used for building other package in the same project? * more?
The xml format has to be altered in a non backward compatible way. The enable/disable tags as direct children of <package> are removed and new children for each block is added. Furthermore we add the same tags to the project tag. That gives us the same configurability as at the package level.
Looks great! Are we planning on automatically converting existing configurations to the new one, once it's live? This would be very much appreciated, I guess. Best, Christoph -- Christoph Thiel, Tech. Project Management, Research & Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2007-03-15 17:13:19 +0100, Christoph Thiel wrote:
Looks great! Are we planning on automatically converting existing configurations to the new one, once it's live? This would be very much appreciated, I guess.
i would convert them on rebuild/checkin... so we dont need to walk over all package/project files. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, on Mittwoch, 14. März 2007, Marcus Rueckert wrote: [...]
3.3. Interaction between "build" and "publish" ------------------------------------------------
3.3.c build disabled and publish enabled -----------------------------------------
If publishing of a package is enabled and you disable a package, the old packages will be purged in the public repository.
I don't think this is a good idea ;-) Use case: You are "playing" with a package update and want to save CPU cycles by disabling all but one build target until everything builds as needed. It would be a bad idea to delete the old, but working packages from the public repository in this case... Or, even simpler: you first click "disable build" and then "disable publish" - if the server is too fast, the packages will be deleted...
The other option is to add a purge command to the api and let the user purge the rpms manually.
Yes, please - that's a much better way.
Use case: This way you can remove broken packages from the repository.
3.3.d build disabled and publish disabled ------------------------------------------
If publishing of a package is disabled when you disable building of a package, the old packages will be preserved.
This would probably also help when "playing" with package updates - but I guess many people will (accidently) not disable publish...
3.3 "usedforbuild" --------------------
The default remains enabled.
Use case: Allow building of gcc snapshots without breaking your own project.
Good idea. If possible, I'd like to have a possibility to use the package for a specific package while basically not using it. Use case: Package foobar needs a brand-new version of gcc to compile, but most other packages work with the gcc version from the distribution. Regards, Christian Boltz -- Diese Message wurde erstellt mit freundlicher Unterstützung eines frei- laufenden Pinguins aus artgerechter Freilandhaltung. Er ist garantiert frei von Micro$oft'schen Viren. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (4)
-
Christian Boltz
-
Christoph Thiel
-
Marcus Rueckert
-
Michal Marek