Just to let people know, I've finished this and have a working kde desktop on a RHEL8 beta vitual machine. After I got about halfway through, things shifted from 1 in 3 packages having problems to 1 in 10, and then things went much faster. Anyway, I'm going to rebuild everything again because I changed where I was building things about 50 packages in, and my %dist tag is different between the two, as well as libraries might be a little different between the two. But since I have the build-order correct, and the src.rpm's already fixed, this should go much faster. Hopefully I should have this where others can try it by the weekend or early next week. For those who are curious there were about 390 packages built. About 350 of them are kde one's, while the rest are supporting packages that aren't in RHEL8. On Mon, Jan 14, 2019 at 6:36 AM Troy Dawson <tdawson@xxxxxxxxxx> wrote: > > So, my work on this is going along slowly but still moving. I'm about > 1/3 way through what was initially 350 packages. > About 1 in 3 packages needs to be tweeked in some way. Usually just > enabling bootstrap and/or disabling kde4 components. > > But I've hit a package I'm having issues with, due to python vs python2/python3. > qt5-qtwebengine > For starters, it has a buildrequires for /usr/bin/python and is > running "python <command>" in the %prep section. > Those were the easy part. > But when the source actually builds, it is using "python" in the > generated Makefiles. That's much more invasive than I've had to get > with any of the other packages. > My real question is this. > Should I file a bugzilla for this (It didn't seem to get the python -> > python2/python3 treatment all the other Fedora packages got) or just > do some type of fix/workaround? > > > On Tue, Jan 8, 2019 at 12:10 PM Troy Dawson <tdawson@xxxxxxxxxx> wrote: > > > > Very Cool. I like that. > > Hundreds of packages and their dependencies only add to the fun. > > I'm going to give it a go and I'll let you know how things work out. > > (Being honest, I've already tried using the "Put everything I can > > think of in a directory and just retry builds until things work" > > approach. That worked on quite a bit, but I can see from the output > > of kdesrc-build that I was missing several fundamental packages.) > > > > Thank You > > > > On Tue, Jan 8, 2019 at 8:13 AM Jan Grulich <jgrulich@xxxxxxxxxx> wrote: > > > > > > Hi, > > > > > > you can use Qt 5 provided by RHEL 8, it should be almost identical to one we > > > have in Fedora. Problem is that I'm not sure you will have all the needed > > > dependencies for all packages. The goal for RHEL 8 was to keep it at minimum > > > regarding number of packages. Also building everything is not an easy task, > > > that's like hundreds of packages (frameworks, kde apps, plasma). Instead of > > > doing builds from rpms, I would most likely use kdesrc-build [1], which will > > > handle all dependencies and build chain for you, it just need to be properly > > > configured. > > > > > > [1] - https://kdesrc-build.kde.org/ > > > > > > Regards, > > > Jan > > > > > > On úterý 8. ledna 2019 16:44:15 CET Troy Dawson wrote: > > > > I know that RHEL8 isn't out yet, but I'd like to run KDE on my RHEL8 > > > > Beta. Even if it's just the basic KDE desktop. > > > > I'm fine building it myself, but I'm having a hard time figuring out > > > > the rebuild flow. > > > > > > > > If I (or anyone) were to rebuild KDE for RHEL8, where do I start? and > > > > then what's next? > > > > > > > > There are base QT5 packages in RHEL8 beta. Do you think I would need > > > > to rebuild QT5? Or just start with RHEL8's QT5 packages. > > > > > > > > Thanks > > > > Troy _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx
