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.
I've adapted the pygobject3.SlackBuild to fix that problem and also provide control over which single, or combination of, python version modules are built. I've sent it to the maintainer hoping that it, or something else which does the same thing, is implemented in the official SlackBuild. My version is at https://github.com/cwilling/slackbui...ct3.SlackBuild (tested with 14.1 and -current).
I've adapted the pygobject3.SlackBuild to fix that problem and also provide control over which single, or combination of, python version modules are built. I've sent it to the maintainer hoping that it, or something else which does the same thing, is implemented in the official SlackBuild. My version is at https://github.com/cwilling/slackbui...ct3.SlackBuild (tested with 14.1 and -current).
chris
Also, for this SlackBuild (and probably others), gnome-common needs a version bump to work in -current. The gnome-common-3.4.0.1 at SBo has (in its gnome-autogen.sh) hard coded versions of automake which it will accept, the highest being 1.11 i.e. it won't accept the automake-1.14.1 which is in -current. I have locally upgraded to gnome-common-3.14.0 and that works fine for me, so far, in -current.
I would have preferred to keep version updates in another topic, but if updates are needed, then so be it if it counts to fix issues with packages and resolve dependencies then it must be done.
the problem is that automake in -stable doesn't get upgraded, thus gnome-common can't be upgraded since SBo is targetting for stable releases
I was referring to -current needing the gnome-common upgrade. I thought (from very first post in this thread) that we're discussing fixes for -current; sorry if I misunderstood. Nevertheless its probably harmless to update gnome-common in -stable, even if the update is not actually needed there.
thanks chris, np for me updating it on my repo for -current: actually I've already pushed the branch, will go in main "current" one at the next global merge.
NetSurf 3.3 was released on 15 Mar 2015
NetSurf 3.3 is primarily a bug-fix release. Several of the front ends have received quite a bit of attention, with new features and improvements; notably the AmigaOS front ends has gained the beginnings of support for AmigaOS 3. We recommend all users upgrade.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.