[Bug 49205] Split the huge Gideon RPM in several RPMs

Simon Hausmann hausmann at kde.org
Wed Oct 16 09:38:05 UTC 2002

On Wed, Oct 16, 2002 at 12:00:44AM +0200, F at lk Brettschneider wrote:
> Hi (Simon)!
> Simon Hausmann wrote:
> >------- You are receiving this mail because: -------
> >You are the assignee for the bug, or are watching the assignee.
> >    
> >http://bugs.kde.org/show_bug.cgi?id=49205     
> >hausmann at kde.org changed:
> >
> >          What    |Removed                     |Added
> >----------------------------------------------------------------------------
> >                CC|                            |hausmann at kde.org
> >            Status|UNCONFIRMED                 |RESOLVED
> >        Resolution|                            |WONTFIX
> >
> >
> >
> >------- Additional Comments From hausmann at kde.org  2002-10-15 23:33 -------
> >You might probably want to report this to feedback at suse.de or 
> >bugzilla.suse.de
> >(if you're a SuSE beta tester and know the password) . There's nothing we 
> >can do
> >about this, as it is SuSE that maintains the spec file / does the 
> >packaging (in
> >your case) .
> >
> But how should they ever know what is a useful split? I suppose they 
> aren't KDevelopers enough to judge a split is useful and furthermore all 
> the useful combinations of the plugins. IMO the KDevelop team must 

In order to package software you need to be aware of the installed
files as well as the dependencies the package has. (try creating an
rpm or debian package and you'll see :)

I have my doubts that Adrian of SuSE is likely to browse the kdevelop
wishlist items for possible suggestions for SuSE rpms ;-)

If you want to force packagers to create multiple rpms then you have
to release multiple source tarballs. Although that does not really
technically force them it at least serves as good 'Wink mit dem
Zaunpfahl' :) . 

The other option is to talk to the packagers and kindly suggest to
them the creation of multiple rpms out of one source package (as in
your wishlist report) .

> define that somehow. Then isn't it good to maintain the spec file by 
> ourselves?

Trust me, you don't want to maintain the different spec files for
all the RPM based distros out there, aside from the fact that I
don't know of any distro that ships and maintainers their spec file
in the upstream source. They usually have their own repository with
all the spec files of all packages. That makes them independent from
upstream resources (human as well as machine wise) .


More information about the KDevelop-devel mailing list