[opensuse-kde] Build Service Repositories Restructuring - Feedback wanted
Hi, it is clear that the current structure of the build service repositories does not fit the demand anymore, and we're trying to think of alternatives that work better. Over the last few days I've been trying to collect the list of problems and put a couple of possible plans together. I would appreciate any feedback, comments or suggestions. Wiki page: http://en.opensuse.org/KDE/Meetings/Buildservice_Projects Feedback either by email, mailing list posting or editing the wiki is possible :) Thanks, Dirk -- RPMLINT information under http://en.opensuse.org/Packaging/RpmLint --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wednesday 28 November 2007 23:32:22 wrote Dirk Mueller:
Hi,
it is clear that the current structure of the build service repositories does not fit the demand anymore, and we're trying to think of alternatives that work better. Over the last few days I've been trying to collect the list of problems and put a couple of possible plans together.
I would appreciate any feedback, comments or suggestions.
regarding the known issue: "Most people who package Qt 4.x related stuff link libqt4 from KDE:Qt, they do not aggregate it or build the repository against KDE:Qt" I consider this as a web UI issue actually. It is really easy to link packages via the "create a source link" button. But it is way harder to see how you can reuse directly another package (via target modification or via the expert target add page.) This is definitive something we need to improve. My first guess would be to add a generic "Add new package" wizard, which could offer the following items: * Create own new source package. * Reuse packages from other project builds (this would need to modify the target definition later on) * Rebuild source from other project. (WARNING: will affect your quota) * Copy in build package from other project and republish it. (WARNING: will affect your quota) Robert, you may want to consider this in your mockup.
Wiki page:
http://en.opensuse.org/KDE/Meetings/Buildservice_Projects
Feedback either by email, mailing list posting or editing the wiki is possible :)
Thanks, Dirk
-- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On 29.11.2007, at 08:56, Adrian Schröter wrote:
On Wednesday 28 November 2007 23:32:22 wrote Dirk Mueller:
Hi,
it is clear that the current structure of the build service repositories does not fit the demand anymore, and we're trying to think of alternatives that work better. Over the last few days I've been trying to collect the list of problems and put a couple of possible plans together.
I would appreciate any feedback, comments or suggestions.
regarding the known issue:
"Most people who package Qt 4.x related stuff link libqt4 from KDE:Qt, they do not aggregate it or build the repository against KDE:Qt"
I consider this as a web UI issue actually. It is really easy to link packages via the "create a source link" button. But it is way harder to see how you can reuse directly another package (via target modification or via the expert target add page.)
This is definitive something we need to improve. My first guess would be to add a generic "Add new package" wizard, which could offer the following items:
* Create own new source package. * Reuse packages from other project builds (this would need to modify the target definition later on) * Rebuild source from other project. (WARNING: will affect your quota) * Copy in build package from other project and republish it. (WARNING: will affect your quota)
Robert, you may want to consider this in your mockup.
Yes, I want. :) Thank you for the information!
Wiki page:
http://en.opensuse.org/KDE/Meetings/Buildservice_Projects
Feedback either by email, mailing list posting or editing the wiki is possible :)
Thanks, Dirk
Cheers, Robert --- Robert Lihm, Webdesigner - Build Service Team SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0 - rlihm@suse.de ____________________________________________________________ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ____________________________________________________________ SUSE - a Novell business --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Thursday 29 November 2007, Adrian Schröter wrote:
I consider this as a web UI issue actually. It is really easy to link packages via the "create a source link" button. But it is way harder to see how you can reuse directly another package (via target modification or via the expert target add page.)
This is definitive something we need to improve. My first guess would be to add a generic "Add new package" wizard, which could offer the following items:
* Create own new source package. * Reuse packages from other project builds (this would need to modify the target definition later on) * Rebuild source from other project. (WARNING: will affect your quota) * Copy in build package from other project and republish it. (WARNING: will affect your quota)
okay, but I dislike the building against another project approach because a) it is hard to find (only via the extra long ultra hidden select box) b) it breaks deps for people who already use the repo c) it usually (by default) breaks the distro name (e.g. the new repository name is "standard", or the one you choose freely) -- RPMLINT information under http://en.opensuse.org/Packaging/RpmLint --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (3)
-
Adrian Schröter -
Dirk Mueller -
Robert Lihm