X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mail.wilcox-tech.com (mail.wilcox-tech.com [45.32.83.9]) by lists.alpinelinux.org (Postfix) with ESMTP id 746425C5A44 for ; Fri, 27 Oct 2017 18:01:17 +0000 (GMT) Received: (qmail 31779 invoked from network); 27 Oct 2017 18:01:14 -0000 Received: from 107-131-85-28.lightspeed.tulsok.sbcglobal.net (HELO ?192.168.1.57?) (awilcox@wilcox-tech.com@107.131.85.28) by mail.wilcox-tech.com with ESMTPA; 27 Oct 2017 18:01:14 -0000 Subject: Re: [alpine-devel] KDE Plasma packaging in Alpine To: Natanael Copa , Jakub Jirutka References: <31b20754-2244-780f-8d98-9ed68478db30@bitmessage.ch> <3B2637BC-EC68-4BC5-85A6-D2700A2381ED@jirutka.cz> <59F2A0E7.1010804@adelielinux.org> <3D888B6C-72A7-49F1-840F-82C3B7EC4876@jirutka.cz> <20171027180108.678254fc@ncopa-desktop.copa.dup.pw> Cc: alpine-dev From: "A. Wilcox" X-Enigmail-Draft-Status: N1110 Organization: =?UTF-8?Q?Ad=c3=a9lie_Linux?= Message-ID: <59F3746A.3090707@adelielinux.org> Date: Fri, 27 Oct 2017 13:01:14 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 In-Reply-To: <20171027180108.678254fc@ncopa-desktop.copa.dup.pw> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 27/10/17 11:01, Natanael Copa wrote: > On Fri, 27 Oct 2017 14:03:05 +0200 Jakub Jirutka > wrote: >> In the light of these arguments, I changed my mind * I*d prefer >> LTS version of KDE to non-LTS. Also I support adding KDE packages >> to Alpine, if Awilfox will help us maintaining them in >> long-term. >=20 > I prefer LTS too if possible. >=20 > We could maybe have the next version of KDE in edge/testing? > similar to what we do with firefox and firefox-esr? I'm not sure what you mean by that, but edge/testing is definitely where I would want KDE to land until it is known to work well on Alpine. > Needs be done carefully though. We did have some confusion with > php7 in community and testing. >=20 >>> The entire team at Ad=E9lie are dead serious about making sure >>> that our packages are rock solid on varied hardware. >>>=20 >>> The reason that we have not already upstreamed our KDE work is >>> that we are still ensuring that it works *everywhere*. We have >>> a few people volunteering to try it out on ARM, and I*m trying >>> to bring up PPC64. >>=20 >>=20 >> I think that this is good enough for adding them to the Alpine*s=20 >> testing repository right after releasing v3.7 (so we can now >> focus on release). >=20 > I agree that we should focus on the v3.7 release now. >=20 > A. Wilcox: What is the current state of 5.8? Do you think it is=20 > realistic to merge it now and have it working without delaying the > v3.7 release too much? The frameworks are ready. They're ABI stable and they work flawlessly on musl. I have no doubt that they would be fine in v3.7. However, that doesn't include the Plasma desktop, just the frameworks... which may not be very useful without the desktop itself. See below. > Are you ok to wait til after Alpine 3.7 release and aim for KDE > 5.12 in Alpine v3.8? My main concern is that we still don't have any display manager capable of launching a KDE session. So you would need to have .xinitrc with: exec ck-launch-session dbus-launch --exit-with-session startkde This doesn't seem like a very nice way to do things. I highly doubt I'll be able to get sddm to work with ConsoleKit2 before v3.7 is done and released. After one week of work I have it communicating with CK2 but not yet creating sessions or reading the seats properly. I can't really speak for 5.12 yet. We of course feel confident that it will be a great release, and they have integrated a lot of our work upstream for it. However, there's always the chance for some breakage as there is with any package release. I don't know when Alpine 3.8 would be shipping and I don't know when a version freeze would happen and so on. There's not a lot of information that I can find that talks about Alpine's release schedule. It looks like, based on past releases, the next one would be in May 2018? If that is the case KDE 5.12 should be very ready by then. FWIW, at the current rate of progress, Ad=E9lie 1.0 is probably due for a release around January 2018. We plan to bump to kernel 4.14 and KDE 5.12 and then release Ad=E9lie 1.5 somewhere in the summer. That looks like it would line up pretty cleanly to being based on Alpine 3.8. No guarantees, obviously, but assuming everything I have said in this message turns out to happen, we would probably be looking at upstreaming KDE Plasma 5.12 in to Alpine some time in February. As I said, I am willing to work on KDE Frameworks (KF5) integration now but I don't know how useful those would be without something using them. All the best, - --arw - --=20 A. Wilcox (awilfox) Project Lead, Ad=E9lie Linux http://adelielinux.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJZ83RnAAoJEMspy1GSK50Uv9wP/29uF5OYS83kA8wsLSl8s43y j0vQjSQ9b+kaK70sOV6tcIRZqUjjFP2X+WUMGDYyzIqercq2D0Wf/7cTYV4ROazP sM5JB5fazMzPD3HQH4hyN4ZIRXKGS3pfjVDVfuEqsIk6FT96ntWvHpxqOKTsahwt GZtyeSfVAsQCLIcmi1FjyKVQRiN2vj52P27s2EeIBljgfah31kmGISo6kD5umQwc Uc6XLD6euOO2C3j7BYRtnrlPICuI+2ClX5ZCjoguuht26Dv5oehlt1n9gD0h2R7F pwbFhVh3KdG5meWhWMLSEXwZ6vbJfeodS0ezJrAIsp3tV4fKNOGCul8mtgvj9toP zwBwImdCPyzLHLwrNwKxSNP/iE1cm3Is9hW3uQAjxJPK6kAiNfg7EA8bzU45/NF0 GQVkdR6d0ETJBCN0EdJf6dRDmLHD2/6GCOc5X9NpfBCVxemB/HfO30PsSP6Nd51h vYNI8lTp1O6/DKf2PFgG7Sr20Na7dGnDWif2IA4T7gUx+q34WHVV8CMPWbnzWega qUVmP4RX9chu7Tdzv2j+vbBvVirNab/ar2oz/Cab8cykLnByW1bQ3gsc+RKrB3q9 N8OQsgFLBv8IgaG0QI11oWnn1HLAH9I6jDgOZQ6jU75ULRQkO6GY42t7yn2EqIBW HY4BE8vG5iQaDLQB8N/8 =3DHyRa -----END PGP SIGNATURE----- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---