SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can cmake 3.6 be added to current? Its required for ppsspp now and this makes it problematic to update build scripts for it when slackware has cmake 3.5.2, even if they would be only for slackware current for now.
is it still too controversial to ask for PAM to be included in the next release?
This thread is more for updates to existing packages as well as necessary required dependencies if any are needed.
You can request it to be added in another thread, but currently PAM is still optional to the system. There are other repositories that add PAM, and some unofficial packages contributed by others, but traditionally, the core system only adds what is required for a functioning and featured system. Unless it becomes a required dependency, rather than a recommended or optional dependency to any existing packages, the chances are what they are, entirely at Patrick's discretion.
This thread is more for updates to existing packages as well as necessary required dependencies if any are needed.
This thread is to request, be it washing machine controlling software :-^
Quote:
Originally Posted by ReaperX7
Unless it becomes a required dependency, rather than a recommended or optional dependency to any existing packages, the chances are what they are, entirely at Patrick's discretion.
...
Because 4.9 is obviously shaping up to be a big release (I haven't
done the actual stats yet, but I think it's the biggest in number of
commits we've ever had), and I think Greg is also planning on making
it an LTS release. The two may be related, with people pushing to get
their stuff ready. Regardless, the more people who help test, and the
earlier in the rc series those people start testing, the better off
we'll be. Hint hint.
...
Xfce has seen some development, maybe it would be worth looking at and pulling in into -current?
In the meantime, there were some bug fix releases, namely:
- xfce4-panel-4.12.1
- xfce4-settings-4.12.1
- xfconf-4.12.1
Maybe it would be worth to spin patches for -14.2?
xfce4-panel-4.12.1 and xfconf-4.12.1 compile without any changes to SlackBuilds.
For xfce4-settings-4.12.1 to build, xfce.xfsettingsd.display.crtc.diff.gz and 0001-Make-sure-icon-NULL-if-no-icon-is-found.patch have to be removed. Those patches are included in the upstream 4.12.1 version.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,015
Rep:
Quote:
Originally Posted by atelszewski
Hi,
Xfce has seen some development, maybe it would be worth looking at and pulling in into -current?
In the meantime, there were some bug fix releases, namely:
- xfce4-panel-4.12.1
- xfce4-settings-4.12.1
- xfconf-4.12.1
Maybe it would be worth to spin patches for -14.2?
xfce4-panel-4.12.1 and xfconf-4.12.1 compile without any changes to SlackBuilds.
For xfce4-settings-4.12.1 to build, xfce.xfsettingsd.display.crtc.diff.gz and 0001-Make-sure-icon-NULL-if-no-icon-is-found.patch have to be removed. Those patches are included in the upstream 4.12.1 version.
--
Best regards,
Andrzej Telszewski
Plus One!
Here is some information on the panel upgrade,
Quote:
+- Long overdue maintenance release.
+- Translation updates.
+- Clock: fixed compiler warnings.
+- Preferences: support for xfpanel-switch (if installed).
+- DirectoryMenu: fixed bugs #10331 and #11742
+- Tasklist: fixed background color issue.
+- ApplicationsMenu: fixed uninitialized variable.
+- make distcheck fix/workaround.
Here comes the real magic; Pat acts like a Mayor: and you looks like are "the voice of crowd".
Yet, as member of crowd, I'm not convinced that "shocking improvements on UTF8 under MacOS" is a must to be upgrade for Slackware Linux...
Oh, wait! MacOS is not even BSD based, like MacOS/X...
You know, Slackware, like any Linux, is Linux not BSD based...
If it bothers you then you could go to a death by committee distro, like say Ubuntu or Debian. Enjoy your systemd there. MacOS now means MacOS X, just to point out, you know, the bloody obvious. A userland improvement really does not matter so much whether the kernel is *BSD, or Linux. Pointing out more obvious. You know if this lack of death of committee bothers you, then why are you using the Linux kernel in the first place? What we have here is a failure to cognate.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.