Didier, Thank you for the excellent and comprehensive reply. I appreciate that you continue to maintain the SLINT project and keep it in sync with the security improvements of Slackware 14.2.
The target device is currently LLVM/LUKS, LILO, Slackware64 14.2 without KDE packages, but with AlienBOB Multilib, VLC, QT5, and many SBO packages, including OpenOffice4.1.7, Scribus, Inkscape, KeePass and keepassxc, Claws-mail with dillo plugin, skypeforlinux, zoom-linux, vivaldi, MasterPDFEditor, XnViewMP, fvwm3 and all the dependencies needed for those applications. I know some of these are available from SLINT, or Salix. Is it possible to continue to use the SBo's if not available from SLINT/Salix? Which brings up the question, do I need to rebuild all the SBo's after upgrading to SLINT? I think I read a Slint Documentation page about using SBo's and special handling, is it still correct? My bigger concern is moving to GRUB, since I'm using LILO now. Is that GRUB2? Can I run GRUB2 in a /boot of 100MG? Thanks again, BrianA_MN |
Hi Brian,
|
@Didier Again thank you for the clarifications. The noted details to be cautious with sbopkg are especially appreciated because I use slackpkg+ to keep 14.2 core and the alienBOB packages up to date and sbotools and sboui to keep the slackbuilds up to date. So there will be some adjustments to administrative tasks on my part. Does SLINTS "update available" notification widget require grub installed, or does it use sbopkg? I was actually thinking of using slackpkg+ to add SLINT repository as priority PRIORITY_PACKAGE, and then simply slackpkg upgrade-all, but I think you are advising against that, am I right?
I'm planning to continue with LILO, but will look into whether I can use LLVM to exand /boot to 200MG in order to use grub. How many initrd's will SLINT support? Currently with LILO I have two in the /boot, which I can select when LILO first starts. One is PV's generic kernel 4.4.yyy release as a backup to my local generic kernel builds of 5.4.yyy. Will I still be able to have a backup kernel incase an issue arises with the latest kernel SLINT releases? The SLINT documents are fairly complete and the SLINT forum has additional information re-read, before asking any more questions. Cheers, BrianA_MN |
1 Attachment(s)
Quote:
Quote:
Quote:
Quote:
Additionally Slint ships the grub-emu utility that you can use in a running system (for instance after a grub update) to check the look and content that will have the the grub menu after rebooting (see attached pic for an example). Better read the Slint documentation here, the one on slint.fr is not up to date. And feel free to ask more questions on our mailing list. |
Quote:
It sounds like you already have QT and VLC in the Slint repository, will the QT and VLC -alien packages need to be re-installed? I used slackpkg+ to install and keep up-to-date the multilib packages, will slapt-get do the same? Quote:
I'll read the referenced documentation site. Since I plan on upgrading a working 14.2 and not re-install, should I remove the SBo versions of packages included with SLINT to avoid the slint<->sbo tug-of-war on the updates? Cheers, BrianA_MN |
Quote:
Quote:
Quote:
Quote:
Cheers, |
Didier, I'll try to keep my questions about a standard upgrade to 14.2.1.2 to this thread. Sorry about polluting the other ANNOUNCE thread with my response on what I was trying to do. I don't really have a testing bed, but once I have 14.2.1.2 installed I can try the -rc releases.
I think I still need to do the dist upgrade from Slackware 14.2 to SLINT 14.2.1.2 with the slapt-get dist-upgrade. I'm trying to be cautious since I have a claws-mail 3.17.7 patched for OAUTH and don't want to loose it. I mention that I use sbotools and it will automatically retain the built packages in a separate designated repository, so when temp is wipedout I don't loose the build, or if a build is bad I can easily go back to the previous version by simply upgradepkg from the repository of old build. It will be interesting to see which SBo packages (there are currently over 508) are replaced by SLINT. Quote:
UPDATE: Actually, slapt-getrc can be set with a CUSTOM class for the multilib repository and it will always be the top priority for the glib and gcc and compat32 packages over Slackware and Slint. Then slint packages, then slackware packages. That's slick and less confusing than slackpkg+ setup with priority_pkg and repository orders. Quote:
Quote:
Stay safe and Cheers, BrianA_MN |
@Didier, Before I proceed with the dist-upgrade I'd like your opinion on a number of questions. Grub2 is installed and working. Slapt-get is installed from slint.fr repository. I've modified the slapt-getrc to include a CUSTOM for multilib repository.
1) Previously you mention the current versions of gcc and glib in Slint are newer to support MATE and XFCE 4.14. However multilib gcc and glibc are based on the Slackware 14.2 gcc and glibc. Would you agree I'll need to rebuild multilib packages for gcc and glibc, as well as remove the CUSTOM statement? 2) If I use CUSTOM for a local repository of SBo pkgs, would that keep the updated claws-mail 3.17.7 which was build with OAUTH2 from being downgraded during a dist-install? I think not and I'll have to upgradepkg from the local repository after the dist-upgrade. Your thoughts? 3) When I installed scribus from slint (slapt-get -install scribus) the application installed with no problem. But when I tried to install inkscape it caused problems and would not run after install. The inkscape install over-wrote the following later rev SBo already present on the system, without notice. avahi, gnome-vfs, libcdr, blas, lapack, numpy3, and potrace. I then had to go back and upgradepkg from my local SBo builds with upgradepkg for avahi, libcdr, blas, lapack, and potrace. When installing packages, does slapt-get check if the packages is already on the system? Does it check the version level? 4) Is there a command like slackpkg has to discover what packages is installed and if an upgrade exists? In slackpkg it is slackpkg search <packagename>. 5) Once dist-upgrade is completed, will LXDM automatically be implemented? I currently have sddm-18 running because slackware-current is moving to sddm. Which brings up... will slint move to sddm in the future Slackware release? Thank you again for your patience and thougts. Cheers, BrianA_MN |
Hi Brian,
Quote:
Quote:
So if your run slapt-get --upgrade after slapt-get -u, slapt-get will propose you to replace the Slint package for claws-mail with yours. You can check typing slapt-get --upgrade -s before slapt-get --upgrade. Quote:
Quote:
Quote:
In Slint you use the login manager you prefer and we have a handy application to pick one or switch to another one: Code:
root[/home/didier]# login-chooser Quote:
|
Quote:
Quote:
Quote:
Can I use the ISO with pkgtools? And would that let me select which apps I'd like? I don't want MATE or KDE, and don't need LibreOffice at this time. If that worked then I can re-install or upgradepkg the SBo's from my local repository, like for any special packages like Claws-mail, Keepass, and others. Your thoughts about the Regex errors and pkgtools? |
Quote:
Quote:
Quote:
Quote:
I think that you have to make a choice:
|
Quote:
I was attracted to SLINT by your efforts to offer a system which considers all types of users by language and by sight. Plus you have later versions of many packages, libraries and even many of the Slackbuilds which are already on the system I use. So it seemed logical to consider moving to SLINT, rather than continuing to wait for Slackware 15 when after 4-1/2 years there is no inkling of an rc0 yet. SLINT would modernize a 14.2 system, with LO over OO, OpenJRE over Oracle Java, and automation of package updating. Questions were introduced when perhaps multilib and claws-mail may need to be re-built, and there are many other packages (including language and speech) which are not of interest at this time. So, I agree with you that a hybrid system would be difficult to manage. My interest is probably a few nuumber of apps, like slapt-get, slapt-src, slapt-update-service, LibreOffice, OpenJRE, XFCE-4.14. Perhaps a few others, but I have to look through the repository more closely. I've appreciated the move to GRUB, and that seems to be working. Maybe I'll figure out the commands to block installation of certain packages during a slapt-get -install-set slint, which would solve my specific interest. Thank you again for all you do in the Slackware community. Cheers, BrianA_MN |
Quote:
|
Quote:
take care, jason |
All times are GMT -5. The time now is 02:48 AM. |