kdesupport Policy

[Allen Winter]

On Monday 25 August 2008 12:52:57 Tom Albers wrote:
> Op zaterdag 23 augustus 2008 01:18 schreef u:
> > Howdy,
> > 
> > The recent build problems in our kdesupport package dependencies
> > needs to be addressed.
> > 
> > I think we need to treat kdesupport libs just like any other external
> > dependency.
> > 
> > Something like the following guidelines:
> > 
> > No KDE code (in trunk) changes should be necessary until:
> >  - a real release of the kdesupport package has been made AN
> >  - that release has been packaged by the "major" distros AND
> >  - an announcement about the needed upgrade is made in advance AND
> >  - people have had time (30 days?) to upgrade to the new packages
> > 
> > For example:
> >   libfoo v1.0 is released.
> >   kde-packagers are notified to please provide packages for their distros.
> >   kde-devel and kde-code-devel are notified that within 30 days their
> >   builds will fail unless they have libfoo v1.0 installed -- that the distros
> >   have been notified and we hope packages will start appearing soon.
> > 
> > People wanting to develop against libfoo v1.0 will need to do so in a work
> > branch.
> > 
> > I need to get out of the habit of building kdesupport all the time -- we should
> > be relying on distro packages where possible.
> > 
> > Comments?
> 
> Sure. That also means that kdesupport can be used as development tree for those applications. In other words, if you use kdesupport instead of distro packages, kdelibs might fail to build.
> 
That's correct.  And if someone complains we can say that "you are using a development
version of Foo which is not supported in KDE yet.  please remove that version and use
the one from your distro instead..."