On Wed, Sep 21, 2011 at 11:28 AM, todd rme <toddrme2178@gmail.com> wrote:
On Mon, Sep 19, 2011 at 1:11 PM, Lubos Lunak <l.lunak@suse.cz> wrote:
On Saturday 17 of September 2011, Raymond Wooninck wrote:
On Saturday 17 September 2011 11:30:03 Ismail Doenmez wrote:
Hi;
Am Sat 17 Sep 2011 11:11:51 AM CEST schrieb todd rme
<toddrme2178@gmail.com>:
I notice in several cases there are several OBS packages with the same source files but with multiple spec files. Examples include kdegames4/kdegames4-carddecks and kdebase4-workspace/python-kdebase4.
From the look of of both it seems to be the case that they can be merged indeed. Any expert opinions?
Another one is to save BuildPower. Most of the noarch packages are build only for the i586 part and NOT on the x86_64 part.
The original reason for building noarch subpackages separately was that older rpm could not build a noarch subpackage from a normal package. At least some of these could be possibly merged back, with the time needed to set up the additional build outweighting the duplicated build of that part and the disk space.
Two immediately come to mind that I am working on right now:
kdegames4/kdegames4-carddecks and kdeartwork4/kdeartwork4-noarch. Should I go ahead and merge these? I am doing substantial changes to both anyway so a merge would not be too difficult compared to everything else.
-Todd
-Todd
I've merged kdegames4 and kdeartwork4. kdeartwork4 has been accepted and the noarch package removed. kdegames4 is still waiting. Besides these, here are the ones that are currently present: kdelibs4 + kdelibs4-apidocs digikam + kipi-plugins + libmediawiki + libkgeomap + libkface koffice2 + koffice2-doc kdebase4-workspace + python-kdebase4 soprano + soprano-backend-virtuoso + soprano-backend-sesame I think that koffice2 and koffice2-doc merging makes sense (in the same way the kdegameds4 and kdeartwork4 merges made sense). digikam's various packages, unlike the other cases, are not all lumped together in a single set of sources. Even if it isn't merged it might be easier if they are all linked. I think that the consensus was to keep kdebase4-workspace and python-kdebase4 seperate, although I would be happy it merge if it makes sense. The last two, kdelibs4 and soprano, I am not sure about. Once again I would be happy to merge these but there might be a good reason not to. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org