Re: [Slackbuilds-users] move cdw category

2022-03-15 Thread B Watson
On 3/16/22, Slackbuilds  wrote:
> Admins,
>
> I should have thought of this (or remembered?) earlier, but IMHO the
> category for cdw should be multimedia instead of system
>
> system/cdw -> multimedia/cdw
>
> to be with the other CD/DVD authoring tools.

I agree in principle, all the CD/DVD creation tools should be in
the same category (not 100% sure whether that should be system or
multimedia)... but then we have a *lot* of builds that are in the
wrong category, or that really belong in two categories (not possible
of course).

For instance, applications that are in python/ because they happen to
be written in python. Or, python modules that should be in python/,
but are in libraries/ instead.

IMO, we should have finer-grained categories, like cd-authoring, or
text-editors, or emulators. But that's unlikely to happen any time
soon (would represent a lot of extra work for the admins, and we're
unpaid volunteers).

If cdw is your build, moving it would be no problem. Or, if you can
convince its maintainer, he can move it easily enough. Otherwise,
it'll have to stay where it is for now.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] move cdw category

2022-03-15 Thread David Chmelik

On 3/15/22 9:18 PM, Slackbuilds wrote:

[...] I should have thought of this (or remembered?) earlier, but IMHO the
category for cdw should be multimedia instead of system

system/cdw -> multimedia/cdw

to be with the other CD/DVD authoring tools. [...]
Since people also make data/OS discs, I think those tools should 
mostly/all be system, just like tools for a floppy disc drive (FDD) 
would be.
    I haven't made audio CDs since mid-to-late 1990s; since then it's 
only been several data CDs/DVDs and dozens OS ones... on certain older 
computers, sometimes a CD will boot better than USB or is the only option...

    I don't think I'm alone on this?
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



[Slackbuilds-users] move cdw category

2022-03-15 Thread Slackbuilds
Admins,

I should have thought of this (or remembered?) earlier, but IMHO the
category for cdw should be multimedia instead of system

system/cdw -> multimedia/cdw

to be with the other CD/DVD authoring tools.

-kb

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



[Slackbuilds-users] Updated list of builds that were removed for 15.0

2022-03-15 Thread B Watson
Since the list I posted before had some stuff that wasn't really
removed, here's a corrected version.

https://slackware.uk/~urchlay/src/sbo-removed-for-15.0.txt

Some of these wouldn't be hard to get building on 15.0. I just
re-added games/rejoystick, it needed a minor tweak to its configure
command (LIBS="-lX11"). Some of them are never going to happen,
e.g. KDE4 apps.

Rest of this mail is the list (same as the URL above).

academic/Mnemosyne: Removed (requires nonexistent PyQtWebEngine dep).
academic/QtiPlot: Removed.
academic/Xyce: Removed (ftb).
academic/abella: Removed (ftb).
academic/avogadro: Removed.
academic/bpp-core: Removed (ftb + no active maintainer).
academic/bpp-phyl-omics: Removed (ftb + no active maintainer).
academic/bpp-phyl: Removed (ftb + no active maintainer).
academic/bpp-popgen: Removed (ftb + no active maintainer).
academic/bpp-seq-omics: Removed (ftb + no active maintainer).
academic/bpp-seq: Removed (ftb + no active maintainer).
academic/bpp1.9-numcalc: Removed (ftb + no active maintainer).
academic/bpp1.9-phyl: Removed (ftb + no active maintainer).
academic/bpp1.9-seq: Removed (ftb + no active maintainer).
academic/bpp1.9-utils: Removed (ftb + no active maintainer).
academic/bppsuite: Removed (ftb + no active maintainer).
academic/coq: Removed (ftb).
academic/drawtiming: Removed (incompatible with the newer gcc).
academic/flashqard: Removed (no qt4-webkit available).
academic/gcompris: Removed.
academic/prank-msa: Removed (ftb + no active maintainer).
academic/treerecs: Removed (ftb + no active maintainer).
academic/vCAPS_coevolution: Removed (ftb + no active maintainer).
audio/Pd-extended: Removed (ftbfs)
audio/cuberok: Removed (unmaintained, qt4).
audio/lastfm: Removed (because libraries/lastfm was removed).
audio/llcon: Removed (abandoned, ftbfs).
audio/spandsp: Removed (roger-router is removed).
business/AssociationSubscribersManager: Removed (abandoned, ftbfs).
business/lemonpos: Removed (requires KDE4).
desktop/cairo-compmgr: Removed.
desktop/crystal: Removed (no more kde4).
desktop/gtk-kde4: Removed (no more kde4).
desktop/homerun: Removed (no more kde4).
desktop/kcometen4: Removed (no more kde4).
desktop/kover: Removed (no more kde4).
desktop/plasma-adjustable-clock: Removed (no more kde4).
desktop/plasma-applet-daisy: Removed (no more kde4).
desktop/plasma-eyasdp: Removed (no more kde4).
desktop/plasma-geek-clock: Removed (no more kde4).
desktop/plasma-widget-menubar: Removed (abandonded ftbfs).
desktop/ptbatterysystemtray: Removed (abandoned upstream).
desktop/qt-recordmydesktop: Removed (needs PyQt4).
desktop/qtcurve: Removed (no more kde4).
desktop/quadkonsole4: Removed (no more kde4).
desktop/quickaccess: Removed (no more kde4).
desktop/recorditnow: Removed (no more kde4).
desktop/screensaver-icon: Removed (source does not exist).
desktop/simon: Removed (no more kde4).
desktop/simplenote: Removed (abandoned by SBo maintainer)
desktop/vertex-maia-themes: Removed.
desktop/vivacious-colors-gtk-icon-theme: Removed (does not work well
with xfce 4.16)
desktop/vivacious-colors-gtk-theme: Removed (does not work well with xfce 4.16)
desktop/xfce4-embed-plugin: Removed (no more libxfce4ui-1).
desktop/yawp: Removed (no more kde4).
development/JSONObject: Removed (incompatible with the newer boost).
development/adoptopenjdk-openj9: Removed (EOL).
development/adoptopenjdk: Removed (EOL).
development/ahven: Removed (needs gprbuild).
development/atom: Removed (no maintainer).
development/bacon: Removed (no maintainer).
development/couchdb: Removed (ftb, no maintainer).
development/eric: Removed (needs PyQt4).
development/flow: Removed (ftb).
development/fsharp: Removed (abandoned).
development/gcclegacy494: Removed (FTB).
development/jdk12: Removed (EOL).
development/jdk13: Removed (EOL).
development/jdk14: Removed (EOL).
development/jdk15: Removed (EOL).
development/jdk16: Removed (EOL).
development/jupyter-ipyleaflet: Removed (abandoned).
development/jupyter-ipywidgets: Removed (abandoned).
development/jupyter-nbdime: Removed (abandoned).
development/jupyter-widgetsnbextension: Removed (abandoned).
development/libbitcoin: Removed (incompat boost 1.78).
development/libodb-boost: Removed (abandoned).
development/libodb-mysql: Removed (abandoned).
development/libodb-pgsql: Removed (abandoned).
development/libodb-qt: Removed (abandoned).
development/libodb-sqlite: Removed (abandoned).
development/libodb: Removed (abandoned).
development/monkey-studio: Removed (no qt4-qscintilla).
development/mono-debugger: Removed (abandoned and ftb).
development/monodevelop: Removed (abandoned).
development/mrustc: Removed (rust now in slackware).
development/nuget: Removed (abandoned).
development/numpy-legacy3: Removed (ftb).
development/odb: Removed (abandoned).
development/qt-creator2: Removed (abandoned).
development/referenceassemblies-pcl: Removed (abandoned).
development/sourcenav: Removed.
development/swift: Removed (abandoned, ftbfs).
development/xemacs: Removed (unmaintained @ SBo)

[Slackbuilds-users] udiskie builds but fails to run on 15.0

2022-03-15 Thread Barry J. Grundy

Hello all,

system/udiskie requires "gi" to run (from pygobject3).  It's currently 
built using python2 with docopt and python2-PyYAML as deps.  The build 
completes without error, but will not run (module gi not found).


Building for python3 fixes the issue.  Pygobject3 and python(3)-PyYAML 
are included in 15.0.  The docopt SB already includes py3 support. So 
the only dep is now docopt.


Thanks,
Barry






___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] netcdf package update

2022-03-15 Thread Greg' Ar Tourter
Hi

I was wondering if it would be ok if I updated netcdf again. I have just
realised that one of my packages (cdo), although it compiles fine with the
version of netcdf in the repo, actually outputs incorrect data in some
cases. compiling against the latest version of netcdf (4.8.1 - which also
brings a few new features including zarr support) fixes the issue.

I would of course check all it dependees (a few of which I maintain anyway)

Cheers

Greg
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Has 15.0 dropped chromium?

2022-03-15 Thread Jeremy Hansen
On Tue, Mar 15, 2022, 1:41 PM Logan Rathbone  wrote:

> On Tue, Mar 15, 2022 at 03:02:43PM EDT, Jeremy Hansen wrote:
> > On Tue, Mar 15, 2022, 12:55 PM Logan Rathbone 
> wrote:
> >
> > > On Mon, Mar 14, 2022 at 01:26:33AM EDT, David Chmelik wrote:
> > > [reversed top-posting, for readability]
> > > > On 3/13/22 8:18 PM, Duncan Roe wrote:
> > >
> > > > Eric (alienBOB) is on Slackware team, so one can trust his newer
> > > > versions with fixes.
> > >
> > > These are very high-quality packages as well, but they are de-googled.
> > > This may be against the grain around these parts, but for me, half the
> > > reason I *do* use Chrome is to get the Google Account integration.
> > >
> >
> > He has both regular chromium and chromium-ungoogled packages.
> >
> > http://www.slackware.com/~alien/slackbuilds/chromium/
> > http://www.slackware.com/~alien/slackbuilds/chromium-ungoogled/
>
> Hm, yes, I have seen this. I think I'll take a second look, but I'm
> thinking ("googled") Chromium and Google Chrome still would have
> different levels of Google integration (Googlization, if you will).
>
> For instance, last time I checked, Google Account integration was not
> working with Alien's (googled) Chromium packages; as I understand, this
> was due to Google's muzzling of unofficial Chromium packages as of 15
> March 2021; see
> https://alien.slackbook.org/blog/google-muzzles-all-chromium-browsers-on-15-march-2021/


Yeah, I have no idea the difference between them, I just saw both on his
repo and that he has 15.0 packages for both.

I imagine there's some difference between them if he's packaging both.

Jeremy
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Has 15.0 dropped chromium?

2022-03-15 Thread Logan Rathbone
On Tue, Mar 15, 2022 at 03:02:43PM EDT, Jeremy Hansen wrote:
> On Tue, Mar 15, 2022, 12:55 PM Logan Rathbone  wrote:
> 
> > On Mon, Mar 14, 2022 at 01:26:33AM EDT, David Chmelik wrote:
> > [reversed top-posting, for readability]
> > > On 3/13/22 8:18 PM, Duncan Roe wrote:
> >
> > > Eric (alienBOB) is on Slackware team, so one can trust his newer
> > > versions with fixes.
> >
> > These are very high-quality packages as well, but they are de-googled.
> > This may be against the grain around these parts, but for me, half the
> > reason I *do* use Chrome is to get the Google Account integration.
> >
> 
> He has both regular chromium and chromium-ungoogled packages.
> 
> http://www.slackware.com/~alien/slackbuilds/chromium/
> http://www.slackware.com/~alien/slackbuilds/chromium-ungoogled/

Hm, yes, I have seen this. I think I'll take a second look, but I'm
thinking ("googled") Chromium and Google Chrome still would have
different levels of Google integration (Googlization, if you will).

For instance, last time I checked, Google Account integration was not
working with Alien's (googled) Chromium packages; as I understand, this
was due to Google's muzzling of unofficial Chromium packages as of 15
March 2021; see 
https://alien.slackbook.org/blog/google-muzzles-all-chromium-browsers-on-15-march-2021/
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Slack 15 gui-ufw not working with webkit2gtk

2022-03-15 Thread B Watson
On 3/14/22, royal.post via SlackBuilds-users
 wrote:
>
> I compiled all the requirements, when trying to run gufw from a term, after
> putting in the root password, nothing happens the GUI doesn't appear, and
> there are no messages at the term.

You sure you don't get any messages when you run it from a terminal?

I see multiple issues. /usr/bin/gufw is a shell script that launches
the real executable with pkexec, and tries to grant access to the
local X server using loginctl as part of the logic...

I think none of this is ever going to work, for users like me (and
probably you) who log in at the console and use 'startx', rather than
a GUI login with runlevel 4.

There's a simpler way to do it. I'm going to replace that wrapper
script.

As for version updates, that's for the maintainer to decide (I'm not
the maintainer, Skaendo is).
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Has 15.0 dropped chromium?

2022-03-15 Thread Jeremy Hansen
On Tue, Mar 15, 2022, 12:55 PM Logan Rathbone  wrote:

> On Mon, Mar 14, 2022 at 01:26:33AM EDT, David Chmelik wrote:
> [reversed top-posting, for readability]
> > On 3/13/22 8:18 PM, Duncan Roe wrote:
>
> > Eric (alienBOB) is on Slackware team, so one can trust his newer
> > versions with fixes.
>
> These are very high-quality packages as well, but they are de-googled.
> This may be against the grain around these parts, but for me, half the
> reason I *do* use Chrome is to get the Google Account integration.
>

He has both regular chromium and chromium-ungoogled packages.

http://www.slackware.com/~alien/slackbuilds/chromium/
http://www.slackware.com/~alien/slackbuilds/chromium-ungoogled/

Jeremy
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Has 15.0 dropped chromium?

2022-03-15 Thread Logan Rathbone
On Mon, Mar 14, 2022 at 01:26:33AM EDT, David Chmelik wrote:
[reversed top-posting, for readability]
> On 3/13/22 8:18 PM, Duncan Roe wrote:
> > google-chrome is in 15.0 extra, as it was in Curent.
> > 
> > Cheers ... Duncan.
> Yes, but that's now significantly old, after maybe security issue(s)
> found/fixed.

Not so; the google-chrome SlackBuild in /extra simply takes the dpkg
that you must manually download from the official Google servers, and
converts that into a Slackware tgz package that matches the version of
the dpkg downloaded.

>     Eric (alienBOB) is on Slackware team, so one can trust his newer
> versions with fixes.

These are very high-quality packages as well, but they are de-googled.
This may be against the grain around these parts, but for me, half the
reason I *do* use Chrome is to get the Google Account integration.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] If you really wont to try - the pain with GCC

2022-03-15 Thread Peter Dambier
On Tue, 15 Mar 2022 12:53:26 +
Erich Ritz via SlackBuilds-users 
wrote:

> --- Original Message ---
>
> On Tuesday, March 15th, 2022 at 4:12 AM, Peter Dambier
>  wrote:
>
> > Hi fello SlackBuilders
> >
> > if you know a little C and if you cherish on old SlackBuild ...
> > you might get overwhelmed with some nessages from gcc-11 that
> > really do not make sense, actually!
> >
> > E.g. gcc-11 can no longer compile avr-gcc.
> >
> > If you are daring enoguh you might want to switch between gcc-5
> > and gcc-11.
> >
> > Here is how I did it.
> >
> > get from good old Slackware 14.2 in one directory - dont install
> > yet!
> >
> > binutils-2.26-x86_64-3.txz
> > gcc-5.3.0-x86_64-3.txz
> > gcc-g++-5.3.0-x86_64-3.txz
> > gcc-gfortran-5.3.0-x86_64-3.txz
> > gcc-gnat-5.3.0-x86_64-3.txz
> > gcc-go-5.3.0-x86_64-3.txz
> > gcc-java-5.3.0-x86_64-3.txz
> > gcc-objc-5.3.0-x86_64-3.txz
> > gettext-0.19.8.1-x86_64-1.txz
> > gmp-6.1.1-x86_64-1.txz
> > libmpc-1.0.3-x86_64-1.txz
> > mpfr-3.1.4-x86_64-1.txz
> >
> > Do the same for Slackware 15.0 in a different directory:
> >
> > binutils-2.37-x86_64-1.txz
> > gcc-11.2.0-x86_64-2.txz
> > gcc-brig-11.2.0-x86_64-2.txz
> > gcc-g++-11.2.0-x86_64-2.txz
> > gcc-gdc-11.2.0-x86_64-2.txz
> > gcc-gfortran-11.2.0-x86_64-2.txz
> > gcc-gnat-11.2.0-x86_64-2.txz
> > gcc-go-11.2.0-x86_64-2.txz
> > gcc-objc-11.2.0-x86_64-2.txz
> > gettext-0.21-x86_64-3.txz
> > gmp-6.2.1-x86_64-3.txz
> > libmpc-1.2.1-x86_64-3.txz
> > mpfr-4.1.0-x86_64-3.txz
> >
> > This may be overkill, depending on what you want to do.
> >
> > Do not removepkg anything!
> >
> > cd into the gcc-5 directory and installpkg *.txz.
> >
> > cd into your SlackBuild. SlackBuild and installpkg
> >
> > cd into the gcc-11 directory and installpkg *.txz
> >
> > Programmes built with gcc-5 will need some librararies ...
> >
> > They do coexist with those from gcc-11 but building is another
> > Story.
> >
> > This is not for the faint of heart.
> >
> > Is it worth the hassle? You decide. I guess 3 from 15 SlackBuilds I
> > was able to rescue with this.
> >
> > The Source is with You.
> >
>
> Peter,
>
> I would not recommend your method.  But to each his own.
>
> gcc5 is available on SBo, as well as avr-gcc.  They integrate into
> the system much nicer than your method.
>
> Another option is to do the old "./configure; make; make install" but
> target /opt/gcc as the DESTDIR.  I did this on Slackware 14.2
> with newer versions of GCC for use with MATLAB.
>
> > Peter
> >
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

Erich,
nor do I. I am glad for the new SlackBuild. That makes my workaround
obsolete.

Cheers
Peter
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] If you really wont to try - the pain with GCC

2022-03-15 Thread Erich Ritz via SlackBuilds-users
--- Original Message ---

On Tuesday, March 15th, 2022 at 4:12 AM, Peter Dambier  
wrote:

> Hi fello SlackBuilders
>
> if you know a little C and if you cherish on old SlackBuild ...
> you might get overwhelmed with some nessages from gcc-11 that
> really do not make sense, actually!
>
> E.g. gcc-11 can no longer compile avr-gcc.
>
> If you are daring enoguh you might want to switch between gcc-5
> and gcc-11.
>
> Here is how I did it.
>
> get from good old Slackware 14.2 in one directory - dont install yet!
>
> binutils-2.26-x86_64-3.txz
> gcc-5.3.0-x86_64-3.txz
> gcc-g++-5.3.0-x86_64-3.txz
> gcc-gfortran-5.3.0-x86_64-3.txz
> gcc-gnat-5.3.0-x86_64-3.txz
> gcc-go-5.3.0-x86_64-3.txz
> gcc-java-5.3.0-x86_64-3.txz
> gcc-objc-5.3.0-x86_64-3.txz
> gettext-0.19.8.1-x86_64-1.txz
> gmp-6.1.1-x86_64-1.txz
> libmpc-1.0.3-x86_64-1.txz
> mpfr-3.1.4-x86_64-1.txz
>
> Do the same for Slackware 15.0 in a different directory:
>
> binutils-2.37-x86_64-1.txz
> gcc-11.2.0-x86_64-2.txz
> gcc-brig-11.2.0-x86_64-2.txz
> gcc-g++-11.2.0-x86_64-2.txz
> gcc-gdc-11.2.0-x86_64-2.txz
> gcc-gfortran-11.2.0-x86_64-2.txz
> gcc-gnat-11.2.0-x86_64-2.txz
> gcc-go-11.2.0-x86_64-2.txz
> gcc-objc-11.2.0-x86_64-2.txz
> gettext-0.21-x86_64-3.txz
> gmp-6.2.1-x86_64-3.txz
> libmpc-1.2.1-x86_64-3.txz
> mpfr-4.1.0-x86_64-3.txz
>
> This may be overkill, depending on what you want to do.
>
> Do not removepkg anything!
>
> cd into the gcc-5 directory and installpkg *.txz.
>
> cd into your SlackBuild. SlackBuild and installpkg
>
> cd into the gcc-11 directory and installpkg *.txz
>
> Programmes built with gcc-5 will need some librararies ...
>
> They do coexist with those from gcc-11 but building is another Story.
>
> This is not for the faint of heart.
>
> Is it worth the hassle? You decide. I guess 3 from 15 SlackBuilds I
> was able to rescue with this.
>
> The Source is with You.
>

Peter,

I would not recommend your method.  But to each his own.

gcc5 is available on SBo, as well as avr-gcc.  They integrate into the system 
much nicer than your method.

Another option is to do the old "./configure; make; make install" but target 
/opt/gcc as the DESTDIR.  I did this on Slackware 14.2 with newer versions 
of GCC for use with MATLAB.

> Peter
>

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



[Slackbuilds-users] Slack 15 gui-ufw not working with webkit2gtk

2022-03-15 Thread royal.post via SlackBuilds-users
Hello,

The Slack 15 SBo for gui-ufwm doesn't seem to work with webkit2gtk 2.34.6

https://slackbuilds.org/repository/15.0/network/gui-ufw/

https://slackbuilds.org/repository/15.0/libraries/webkit2gtk/

I compiled all the requirements, when trying to run gufw from a term, after 
putting in the root password, nothing happens the GUI doesn't appear, and there 
are no messages at the term.

22.04 is the latest version of gufw, it would be greatly appreciated if we can 
get an updated SBo for gufw.

https://github.com/costales/gufw

THANKS___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



[Slackbuilds-users] If you really wont to try - the pain with GCC

2022-03-15 Thread Peter Dambier
Hi fello SlackBuilders

if you know a little C and if you cherish on old SlackBuild ...

you might get overwhelmed with some nessages from gcc-11 that
really do not make sense, actually!

E.g. gcc-11 can no longer compile avr-gcc.

If you are daring enoguh you might want to switch between gcc-5
and gcc-11.

Here is how I did it.

get from good old Slackware 14.2 in one directory - dont install yet!

binutils-2.26-x86_64-3.txz
gcc-5.3.0-x86_64-3.txz
gcc-g++-5.3.0-x86_64-3.txz
gcc-gfortran-5.3.0-x86_64-3.txz
gcc-gnat-5.3.0-x86_64-3.txz
gcc-go-5.3.0-x86_64-3.txz
gcc-java-5.3.0-x86_64-3.txz
gcc-objc-5.3.0-x86_64-3.txz
gettext-0.19.8.1-x86_64-1.txz
gmp-6.1.1-x86_64-1.txz
libmpc-1.0.3-x86_64-1.txz
mpfr-3.1.4-x86_64-1.txz

Do the same for Slackware 15.0 in a different directory:

binutils-2.37-x86_64-1.txz
gcc-11.2.0-x86_64-2.txz
gcc-brig-11.2.0-x86_64-2.txz
gcc-g++-11.2.0-x86_64-2.txz
gcc-gdc-11.2.0-x86_64-2.txz
gcc-gfortran-11.2.0-x86_64-2.txz
gcc-gnat-11.2.0-x86_64-2.txz
gcc-go-11.2.0-x86_64-2.txz
gcc-objc-11.2.0-x86_64-2.txz
gettext-0.21-x86_64-3.txz
gmp-6.2.1-x86_64-3.txz
libmpc-1.2.1-x86_64-3.txz
mpfr-4.1.0-x86_64-3.txz

This may be overkill, depending on what you want to do.

Do not removepkg anything!
cd into the gcc-5 directory and installpkg *.txz.
cd into your SlackBuild. SlackBuild and installpkg
cd into the gcc-11 directory and installpkg *.txz

Programmes built with gcc-5 will need some librararies ...
They do coexist with those from gcc-11 but building is another Story.

This is not for the faint of heart.
Is it worth the hassle? You decide. I guess 3 from 15 SlackBuilds I
was able to rescue with this.

The Source is with You.
Peter
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/