[Slackbuilds-users] meson template

[Logan Rathbone]

Hey all,

Couple of thoughts on the meson template.

First, --buildtype should probably be "plain" and not "release", because
"release" will stick a -O3 in there regardless of what CFLAGS are set
to -- yes, the CFLAGS passed in the standard template will follow and
override that, but it seems to be a cleaner approach to use "plain"
which will give full control over the debug and optimization flags.

I have seen some meson SlackBuilds that don't pass --buildtype at all,
and so what will land up happening there is, meson will default to
--buildtype=debug, which sticks a -g in there, so the standard Slackware
CFLAGS patched into the build command line will follow that, resulting
in an optimized build with debugging symbols. Yes, 'strip' will (I
assume) get rid of those, but it is leaving the door open for
unnecessary complexity and possible clashes that may serve to confuse.

As well, I would suggest -v be added to the ninja command, so that the
build command lines will actually show when the compile is happening,
similar to what a standard GNU make command would show. This will also
make it easier to track down issues with build flags (if any) that may
arise.

Thanks,
Logan (poprocks)
___
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] Updating Redis - and whats depends on it...

[Arnaud via SlackBuilds-users]

Hi everybody,

I'm in the process of taking over Redis and updating it (from 4.0.9 
released 4 years ago, to 6.2.6).
That works pretty nicely, but a few projects are depending on it, and are 
pretty outdated.

 - libraries/php-redis: May be bumped from 4.2.0 to 5.3.7, but seems to work 
fine anyway. Though its maintainer, Ebben Aries, hasn't been active in 2 years.
I will post an update for it, and if nobody maintains it by two weeks, I'll 
take over, as it is kinda linked to redis.

 - system/redis-py: Also very obsolete (2.10.5 is more than 6 years old !), 
builds for python2 (we ought to mercifully kill that beast), and its maintainer 
is very much active here.
So Dimitris, do you want me to handle that one for you ?

 - system/trmaid: builds on Python2 (again !?), but its dependencies are not 
all python2. Namely feedparser builds only Python3. Hence this will not work.
I don't very much want to take over that one, but I will update it if nobody 
does, just so that it works.

 - network/openvas-libraries: another outdated thingy. OpenVAS is still pretty 
much active, but it seems that openvas-libraries in itself doesn't exist 
anymore, the whole bunch of SlackBuilds relating to OpenVAS ought to be 
reworked, and I don't really want to do that. Its maintainer, Kent Fritz, seems 
inative for 1 year and a half. I won't do anything about it, and I don't know 
if updating Redis will break it, but since it doesn't build anyway (source 
isn't available anymore), that won't change much.
Maybe remove all (openvas-cli, openvas-scanner, openvas-libraries), if nobody 
wants to take over maintainership there ?

To summarize :
 - I will post updates for php-redis, redis-py and trmaid, if nobody steps up 
soon.
 - I will take over maitainership of php-redis in a few weeks if there is still 
no active maintainer.
 - I'm willing to take over redis-py from Dimitris Zlatanidis, because it seems 
pertinent since I will be maintainer of Redis itself.

 - I don't especially want to maintain trmaid, I'm just OK to make it work 
today.
 - I will not look into OpenVAS.


Cheers,

- Yth / Arnaud
___
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/