<br><br><div class="gmail_quote">On Fri, Jun 3, 2011 at 9:11 AM, Eric Hameleers <span dir="ltr"><<a href="mailto:alien@slackware.com">alien@slackware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<div><div></div><div class="h5"><br>
<br>
On Fri, 3 Jun 2011, Jeremy Whiting wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dirk, all,<br>
<br>
As you may or may not know kdeaccessibility and kdeutils are ready to<br>
migrate to git (when the freeze is over, don't worry). And we'd like to<br>
know what the feeling is about the best time to migrate to minimize<br>
packaging/releasing stresses. We'd also like to know what<br>
packagers/release-team think of the split repos already done in kde-edu,<br>
etc. Should we provide artificial monolithic tarballs?<br>
<br>
thanks,<br>
Jeremy Whiting<br>
</blockquote>
<br></div></div>
Hi Jeremy<br>
<br>
Thanks for asking this, really appreciated.<br></blockquote><div><br>It needs discussing, so I brought it up. <br></div><div> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I would feel very relieved if the old monolithic tarballs would stay as a download option. Even if the release team maintains a series of scripts that makes a controlled checkout of monolithic tarballs possible for packagers, that would be an acceptible solution.<br>
</blockquote><div><br>As a developer preferring split git repos I'm not against this solution, assuming dirk wants to go for this. My plan for kdeaccessibility is to make one simple CMakeLists.txt that can be used with a tarball of each application beneath it to simply create what exists in svn now. <br>
</div><div> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I expressed my thoughts on the split of kdeedu in an earlier post and coincidentally I fired up this discussion on my blog and the SLackware forum a few hours ago... Slackware will have to consider dropping KDE if we are confronted with source fragmentation. We are a small team and can not accept the added burden of maintaining a fragmented KDE based desktop environment. Fragmenting the source tarballs may be only one step but seeing what happens in GNOME land, with Redhat employees forcibly pushing people into directions they do not want to be taken, I would welcome it if KDE would remain the sane, independent desktop enviroment, or even Software Collection, that I have come to love.<br>
</blockquote><div><br>I was involved with the kdeedu split and I agree it wasn't very well done. Part of that was bad assumptions on my part, but I think we've learned from the mistakes made there. I also don't see how smaller tarballs == more burden, but I've never been a packager. I don't see how it creates something different than the "sane, independent desktop environment" either, could you explain that a bit?<br>
<br>thanks,<br>Jeremy<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Cheers, Eric<br>
<br>
- -- Eric Hameleers <<a href="mailto:alien@slackware.com" target="_blank">alien@slackware.com</a>><br>
Jabber: <a href="mailto:alien@jabber.xs4all.nl" target="_blank">alien@jabber.xs4all.nl</a><br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.9 (GNU/Linux)<br>
Comment: For info see <a href="http://quantumlab.net/pine_privacy_guard/" target="_blank">http://quantumlab.net/pine_privacy_guard/</a><br>
<br>
iEYEARECAAYFAk3o+cAACgkQXlaqr6dcvaC6dgCfeQLtEetvS4t/MEZmIFkrgsEg<br>
naIAn12z4bp/1EjO00dKiL/HkVizoRVR<br>
=3XmU<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div><br>