Re: [blfs-dev] BLFS tagging is finished
Pierre Labastie wrote: On 29/09/2015 20:43, Bruce Dubbs wrote: OK, tagging is finally finished and all tickets for 7.8 are closed. Let's take a day to review and fix up any outstanding issues. If anyone knows of something else that needs to be fixed, please speak up here. If nothing comes up, I plan on releasing LFS-7.8 and BLFS-7.8 stable versions on Thursday, October 1st. I do not know whether KF5-intro is correct in the /usr part, and also, it seems to me that there is some redundancy in the parts added to /etc/profile.d/qt5.sh and /etc/profiles.d/kf5.sh (in the /opt/kf5 case). Problem is: there are 4 cases: - Qt5 in /usr, Kf5 in /usr - Qt5 in /usr, Kf5 in /opt - Qt5 in /opt, Kf5 in /usr - Qt5 in /opt, Kf5 in /opt, which, although not recommended (only thelast one is), are all possible according to the book. I am not sure all cases are covered. In reviewing the /usr install setuup for kf5, all the pathappend statements depend on the location of qt5. We do have a note in the qt5 section about installing in /usr/bin/qt5 and similar qt5 subdirectories of other system directories. This is my analysis: If qt5 is in /usr/bin/qt5 (and similar), then we need pathappend /usr/lib/qt5/plugins QT_PLUGIN_PATH If it is in /opt, then we need: pathappend /opt/qt5/plugins QT_PLUGIN_PATH Actually, the script should be appended to /etc/profile.d/qt5.sh, not /etc/profile.d/kf5.sh. cat >> /etc/profile.d/qt5.sh << "EOF" # Begin Qt5 changes for KF5 # Assuming $QT5DIR == '/usr' pathappend /usr/lib/qt5/plugins QT_PLUGIN_PATH pathappend /usr/lib/qt5/qml QML_IMPORT_PATH pathappend /usr/lib/qt5/qml QML2_IMPORT_PATH # End Qt5 changes for KF5 EOF We also need to add pathappend /usr/bin/qt5 PATH to the qt5.sh in the qt5 section of the book. Does this look right to you? -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS tagging is finished
Pierre Labastie wrote: I just got an error building frameworks: in kdoctools-5.14.0: - -- Could NOT find PerlModules_URI::Escape (missing: PerlModules_URI_Escape_FOUND) we have URI-1.69 in perl modules (which contains URI/Escape), but I do not see it in dependencies. Confirmed. Updated dependencies at revision 16491. Also commented out baloo. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS tagging is finished
Fernando de Oliveira wrote: Bruce, I asked this privately, but I am sure you lost in the multitude of things you are doing. I would like to thank Denis Mugnier for his many contributions with the "Short Descriptions", which I consider a good improvement in BLFS. I don't know if in the release announcement there is a place mentioning this improvement. But I believe we all are grateful to Denis by his constant work. Thanks for the reminder. I will add him to the release announcement. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS tagging is finished
Bruce, I asked this privately, but I am sure you lost in the multitude of things you are doing. I would like to thank Denis Mugnier for his many contributions with the "Short Descriptions", which I consider a good improvement in BLFS. I don't know if in the release announcement there is a place mentioning this improvement. But I believe we all are grateful to Denis by his constant work. -- []s, Fernando, aka SÃsifo -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS tagging is finished
On 30/09/2015 19:18, Bruce Dubbs wrote: > Pierre Labastie wrote: >> On 29/09/2015 20:43, Bruce Dubbs wrote: >>> OK, tagging is finally finished and all tickets for 7.8 are closed. >>> >>> Let's take a day to review and fix up any outstanding issues. If anyone >>> knows >>> of something else that needs to be fixed, please speak up here. >>> >>> If nothing comes up, I plan on releasing LFS-7.8 and BLFS-7.8 stable >>> versions >>> on Thursday, October 1st. >>> >> >> I do not know whether KF5-intro is correct in the /usr part, and also, it >> seems to me that there is some redundancy in the parts added to >> /etc/profile.d/qt5.sh and /etc/profiles.d/kf5.sh (in the /opt/kf5 case). >> Problem is: there are 4 cases: >> - Qt5 in /usr, Kf5 in /usr >> - Qt5 in /usr, Kf5 in /opt >> - Qt5 in /opt, Kf5 in /usr >> - Qt5 in /opt, Kf5 in /opt, which, although not recommended (only thelast one >> is), are all possible according to the book. I am not sure all cases are >> covered. > > In reviewing the /usr install setuup for kf5, all the pathappend statements > depend on the location of qt5. We do have a note in the qt5 section about > installing in /usr/bin/qt5 and similar qt5 subdirectories of other system > directories. > > This is my analysis: > > If qt5 is in /usr/bin/qt5 (and similar), then we need > > pathappend /usr/lib/qt5/plugins QT_PLUGIN_PATH > > If it is in /opt, then we need: > > pathappend /opt/qt5/plugins QT_PLUGIN_PATH > > Actually, the script should be appended to /etc/profile.d/qt5.sh, not > /etc/profile.d/kf5.sh. > > > cat >> /etc/profile.d/qt5.sh << "EOF" > # Begin Qt5 changes for KF5 > > # Assuming $QT5DIR == '/usr' > > pathappend /usr/lib/qt5/plugins QT_PLUGIN_PATH > pathappend /usr/lib/qt5/qml QML_IMPORT_PATH > pathappend /usr/lib/qt5/qml QML2_IMPORT_PATH > > # End Qt5 changes for KF5 > EOF > > We also need to add > > pathappend /usr/bin/qt5 PATH > > to the qt5.sh in the qt5 section of the book. > > > Does this look right to you? > > -- Bruce > I think I would need to test. I guess it would be OK, though. The only test I have done is : KF5 in /usr, Qt5 in /opt. Then I used: -- cat > /etc/profile.d/kf5.sh << "EOF" # Begin /etc/profile.d/kf5.sh . /etc/profile.d/qt5.sh export KF5_PREFIX=/usr pathappend /usr/lib/qt5/plugins QT_PLUGIN_PATH pathappend $QT5DIR/plugins QT_PLUGIN_PATH pathappend /usr/lib/qt5/qml QML_IMPORT_PATH pathappend $QT5DIR/qml QML_IMPORT_PATH pathappend /usr/lib/qt5/qml QML2_IMPORT_PATH pathappend $QT5DIR/qml QML2_IMPORT_PATH # End /etc/profile.d/kf5.sh EOF and Qt5.sh as per the Qt5 page instructions. I could build (not tested yet, still have to build a wm) LXQt with this setup. Now, I think it'd be better to have everything in qt5.sh, except the KF5_PREFIX part. I think that's all I can say before release... Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS tagging is finished
On 30/09/2015 05:50, Bruce Dubbs wrote: Pierre Labastie wrote: I just got an error building frameworks: in kdoctools-5.14.0: - /usr/share/cmake-3.3/Modules/FindPackageHandleStandardArgs.cmake:148 (message): Could NOT find PerlModules (missing: PerlModules_all_modules_found URI::Escape) - we have URI-1.69 in perl modules (which contains URI/Escape), but I do not see it in dependencies. It is late here. I'll tell you more tomorrow. Yes, Having URI allows kdoctools to build. But I found also that the LMDB dependency has not been addressed (see http://lists.linuxfromscratch.org/pipermail/blfs-dev/2015-September/031151.html). It's required for baloo-kf5 and we do not have it in the book. I do not know about the xcb-... packages mentionned in the thread. I do not know what uses baloo-kf5 in the book, now that plasma has been removed. Maybe, just comment out baloo? Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS tagging is finished
Pierre Labastie wrote: I think I would need to test. I guess it would be OK, though. The only test I have done is : KF5 in /usr, Qt5 in /opt. Then I used: -- cat > /etc/profile.d/kf5.sh << "EOF" # Begin /etc/profile.d/kf5.sh . /etc/profile.d/qt5.sh export KF5_PREFIX=/usr pathappend /usr/lib/qt5/plugins QT_PLUGIN_PATH pathappend $QT5DIR/plugins QT_PLUGIN_PATH pathappend /usr/lib/qt5/qml QML_IMPORT_PATH pathappend $QT5DIR/qml QML_IMPORT_PATH pathappend /usr/lib/qt5/qml QML2_IMPORT_PATH pathappend $QT5DIR/qml QML2_IMPORT_PATH # End /etc/profile.d/kf5.sh EOF and Qt5.sh as per the Qt5 page instructions. I could build (not tested yet, still have to build a wm) LXQt with this setup. Now, I think it'd be better to have everything in qt5.sh, except the KF5_PREFIX part. I made some clarifications. They should be OK for release, but please review. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS tagging is finished
Pierre Labastie wrote: On 30/09/2015 05:50, Bruce Dubbs wrote: Pierre Labastie wrote: I just got an error building frameworks: in kdoctools-5.14.0: - /usr/share/cmake-3.3/Modules/FindPackageHandleStandardArgs.cmake:148 (message): Could NOT find PerlModules (missing: PerlModules_all_modules_found URI::Escape) - we have URI-1.69 in perl modules (which contains URI/Escape), but I do not see it in dependencies. It is late here. I'll tell you more tomorrow. Yes, Having URI allows kdoctools to build. But I found also that the LMDB dependency has not been addressed (see http://lists.linuxfromscratch.org/pipermail/blfs-dev/2015-September/031151.html). It's required for baloo-kf5 and we do not have it in the book. I do not know about the xcb-... packages mentionned in the thread. I do not know what uses baloo-kf5 in the book, now that plasma has been removed. Maybe, just comment out baloo? Yes, I'll do that. We only need the kf5 version of baloo for plasma. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS tagging is finished
On 29/09/2015 20:43, Bruce Dubbs wrote: > OK, tagging is finally finished and all tickets for 7.8 are closed. > > Let's take a day to review and fix up any outstanding issues. If anyone knows > of something else that needs to be fixed, please speak up here. > > If nothing comes up, I plan on releasing LFS-7.8 and BLFS-7.8 stable versions > on Thursday, October 1st. > I do not know whether KF5-intro is correct in the /usr part, and also, it seems to me that there is some redundancy in the parts added to /etc/profile.d/qt5.sh and /etc/profiles.d/kf5.sh (in the /opt/kf5 case). Problem is: there are 4 cases: - Qt5 in /usr, Kf5 in /usr - Qt5 in /usr, Kf5 in /opt - Qt5 in /opt, Kf5 in /usr - Qt5 in /opt, Kf5 in /opt, which, although not recommended (only thelast one is), are all possible according to the book. I am not sure all cases are covered. Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS tagging is finished
Pierre Labastie wrote: On 29/09/2015 20:43, Bruce Dubbs wrote: OK, tagging is finally finished and all tickets for 7.8 are closed. Let's take a day to review and fix up any outstanding issues. If anyone knows of something else that needs to be fixed, please speak up here. If nothing comes up, I plan on releasing LFS-7.8 and BLFS-7.8 stable versions on Thursday, October 1st. I just got an error building frameworks: in kdoctools-5.14.0: - -- Could NOT find PerlModules_URI::Escape (missing: PerlModules_URI_Escape_FOUND) CMake Error at /usr/share/cmake-3.3/Modules/FindPackageHandleStandardArgs.cmake:148 (message): Could NOT find PerlModules (missing: PerlModules_all_modules_found URI::Escape) Call Stack (most recent call first): /usr/share/cmake-3.3/Modules/FindPackageHandleStandardArgs.cmake:388 (_FPHSA_FAILURE_MESSAGE) cmake/FindPerlModules.cmake:77 (find_package_handle_standard_args) cmake/uriencode.cmake:34 (find_package) src/CMakeLists.txt:4 (kdoctools_encode_uri) -- Configuring incomplete, errors occurred! - we have URI-1.69 in perl modules (which contains URI/Escape), but I do not see it in dependencies. It is late here. I'll tell you more tomorrow. I didn't see that, but I generally build all perl modules in the book the first time any package wants any perl module. I do not have a problem adding that as a dependency. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
