kdesupport Policy

[Michael Pyne]

On Tuesday 26 August 2008, Riccardo Iaconelli wrote:
> On Tuesday 26 August 2008 01:30:06 Allen Winter wrote:
> > 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..."
>
> I'm not sure I will like this idea.
> First off, it will break many (all?) scripts, including the widely used
> kdesvn-build.

You can use the branch option to control what version of kdesupport you build.  
You also do not *need* to build kdesupport unless you need to install packages 
from it (which if only distro packages are required may not be necessary).

If it really becomes a problem then we can copy the latest batch of release 
changes to a special kdesupport tag and just bump that as needed for use with 
the kdesvn-build tag option.

i.e. phonon 4.2, strigi 0.5.10, etc. go into /tags/kdesupport/4.1.0 or 
something like that, a tag doesn't *have* to be a simple copy of some other 
branch, we can "cherry pick" into a tag as necessary.

> I'm ok by treating kdesupport as external dependency, less ok if I can't
> compile it anymore to build KDE.

Yes, I think it should be possible to build kdesupport and have it work but 
it's not fair to those who just need one module to have to build more stuff 
out of SVN IMO.

Regards,
 - Michael Pyne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/release-team/attachments/20080826/92afbb1f/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/release-team/attachments/20080826/92afbb1f/attachment.sig