Re: [Slackbuilds-users] My -current scripts
On 2021-04-17 4:03 pm, Eugen Wissner wrote: On Sat, Apr 17, 2021 at 03:51:45PM -0500, Gerardo Zamudio wrote: On 2021-04-17 3:05 pm, Eugen Wissner wrote: > On Sat, Apr 17, 2021 at 01:50:22PM -0500, Gerardo Zamudio wrote: > > On 2021-04-17 1:18 am, Eugen Wissner wrote: > > > Hi, > > > > > > I would like to ask to remove the following SlackBuilds: > > > > > > - opendbx: It builds on current, but opendbx doesn't seem to be active, > > > the last release was in 2012 and nothing depends on it. > > > > > > > > > Eugen > > > > I can take OpenDBX. I maintain OpenDKIM and OpenDBX is required if > > MySQL > > support is going to be compiled in (see README). > > > > Regards > > Gerardo Zamudio > > Ah, OpenDKIM was probably the reason I maintained OpenDBX. Two years ago > I switched to rspamd and forgot about OpenDBX. Sorry, my fault. Are you keeping it then? If you actually use it, it is surely in better hands with you. OK, thank you. ___ 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] My -current scripts
On Sat, Apr 17, 2021 at 03:51:45PM -0500, Gerardo Zamudio wrote: > On 2021-04-17 3:05 pm, Eugen Wissner wrote: > > On Sat, Apr 17, 2021 at 01:50:22PM -0500, Gerardo Zamudio wrote: > > > On 2021-04-17 1:18 am, Eugen Wissner wrote: > > > > Hi, > > > > > > > > I would like to ask to remove the following SlackBuilds: > > > > > > > > - opendbx: It builds on current, but opendbx doesn't seem to be active, > > > > the last release was in 2012 and nothing depends on it. > > > > > > > > > > > > Eugen > > > > > > I can take OpenDBX. I maintain OpenDKIM and OpenDBX is required if > > > MySQL > > > support is going to be compiled in (see README). > > > > > > Regards > > > Gerardo Zamudio > > > > Ah, OpenDKIM was probably the reason I maintained OpenDBX. Two years ago > > I switched to rspamd and forgot about OpenDBX. Sorry, my fault. > > Are you keeping it then? If you actually use it, it is surely in better hands with you. ___ 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] My -current scripts
On 2021-04-17 3:05 pm, Eugen Wissner wrote: On Sat, Apr 17, 2021 at 01:50:22PM -0500, Gerardo Zamudio wrote: On 2021-04-17 1:18 am, Eugen Wissner wrote: > Hi, > > I would like to ask to remove the following SlackBuilds: > > - opendbx: It builds on current, but opendbx doesn't seem to be active, > the last release was in 2012 and nothing depends on it. > > > Eugen I can take OpenDBX. I maintain OpenDKIM and OpenDBX is required if MySQL support is going to be compiled in (see README). Regards Gerardo Zamudio Ah, OpenDKIM was probably the reason I maintained OpenDBX. Two years ago I switched to rspamd and forgot about OpenDBX. Sorry, my fault. Are you keeping it then? ___ 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] SlackBuilds-users Digest, Vol 180, Issue 13
Ok, thanks for the update. But please do not carry over PDFshuffler from 14.2 to the 15.0 repo Cheers, Rob On Sat, 17 Apr 2021 05:13:20 + slackbuilds-users-requ...@slackbuilds.org wrote: > Message: 1 > Date: Fri, 16 Apr 2021 20:27:23 +0100 > From: sborg63 > To: "SlackBuilds.org Users List" , > > Subject: Re: [Slackbuilds-users] Development Cycle Towards 15.0 > Repository SlackBuilds-users Digest, Vol 180, Issue 12 > Message-ID: <20210416202723.5279b7ac@knotsUL> > Content-Type: text/plain; charset=US-ASCII > > Hi Willy, > > When would it be possible to submit scripts for packages that only run > on current and that should replace outdated, no-longer maintained > (e.g python2-only) packages that are in the repository for 14.2 atm? > > For example I maintain PDF-shuffler which should be dropped. This I > would like to replace in the 15.0 repository with PDFarranger plus > Pike PDF, which work fine for me on current > (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger > https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). > PikePDF relies on a version of qpdf not available in stock 14.2. > > Good luck with the work ahead... > > Rob > > > > Message: 2 > > Date: Fri, 16 Apr 2021 17:27:07 +0700 > > From: Willy Sudiarto Raharjo > > To: "SlackBuilds.org Users List" > > Subject: [Slackbuilds-users] Development Cycle Towards 15.0 > > Repository Message-ID: > > > > Content-Type: text/plain; charset="utf-8" > > > -- > > Message: 2 > Date: Fri, 16 Apr 2021 20:32:00 +0100 > From: Dave Woodfall > To: slackbuilds-users@slackbuilds.org > Subject: Re: [Slackbuilds-users] Development Cycle Towards 15.0 > Repository SlackBuilds-users Digest, Vol 180, Issue 12 > Message-ID: <20210416193200.GS5008@localhost> > Content-Type: text/plain; charset=utf-8 > > Hi Rob, > > When submissions open again, and we will be in 15.0, which would be > the correct time. > > Dave > > Slackbuilds Users put forth the > proposition: > > Hi Willy, > > When would it be possible to submit scripts for packages that only > > run on current and that should replace outdated, no-longer > > maintained (e.g python2-only) packages that are in the repository > > for 14.2 atm? For example I maintain PDF-shuffler which should be > > dropped. This I would like to replace in the 15.0 repository with > > PDFarranger plus Pike PDF, which work fine for me on current > > (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger > > https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). > > PikePDF relies on a version of qpdf not available in stock 14.2. > > Good luck with the work ahead... > > Rob > > > > > > Message: 2 > > > Date: Fri, 16 Apr 2021 17:27:07 +0700 > > > From: Willy Sudiarto Raharjo > > > To: "SlackBuilds.org Users List" > > > Subject: [Slackbuilds-users] > > > Development Cycle Towards 15.0 Repository Message-ID: > > > > > > Content-Type: text/plain; charset="utf-8" > > -- > Dave > > > -- > > Message: 3 > Date: Sat, 17 Apr 2021 07:34:35 +0700 > From: Willy Sudiarto Raharjo > To: slackbuilds-users@slackbuilds.org > Subject: Re: [Slackbuilds-users] Development Cycle Towards 15.0 > Repository SlackBuilds-users Digest, Vol 180, Issue 12 > Message-ID: > Content-Type: text/plain; charset="utf-8" > > > When submissions open again, and we will be in 15.0, which would be > > the correct time. > > > > Dave > > > >> Hi Willy, > >> When would it be possible to submit scripts for packages that only > >> run on current and that should replace outdated, no-longer > >> maintained (e.g python2-only) packages that are in the repository > >> for 14.2 atm? For example I maintain PDF-shuffler which should be > >> dropped. This I would like to replace in the 15.0 repository with > >> PDFarranger plus Pike PDF, which work fine for me on current > >> (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger > >> https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). > >> PikePDF relies on a version of qpdf not available in stock 14.2. > >> Good luck with the work ahead... > > Hi Rob > > Yes, i agree with Dave > once 15.0 repo is ready, you can submit new scripts > for now, we will focus on getting 15.0 ready first as base for future > new scripts > > ___ 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] My -current scripts
On Sat, Apr 17, 2021 at 01:50:22PM -0500, Gerardo Zamudio wrote: > On 2021-04-17 1:18 am, Eugen Wissner wrote: > > Hi, > > > > I would like to ask to remove the following SlackBuilds: > > > > - opendbx: It builds on current, but opendbx doesn't seem to be active, > > the last release was in 2012 and nothing depends on it. > > > > > > Eugen > > I can take OpenDBX. I maintain OpenDKIM and OpenDBX is required if MySQL > support is going to be compiled in (see README). > > Regards > Gerardo Zamudio Ah, OpenDKIM was probably the reason I maintained OpenDBX. Two years ago I switched to rspamd and forgot about OpenDBX. Sorry, my fault. ___ 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] My -current scripts
On 2021-04-17 1:18 am, Eugen Wissner wrote: Hi, I would like to ask to remove the following SlackBuilds: - opendbx: It builds on current, but opendbx doesn't seem to be active, the last release was in 2012 and nothing depends on it. Eugen I can take OpenDBX. I maintain OpenDKIM and OpenDBX is required if MySQL support is going to be compiled in (see README). Regards Gerardo Zamudio ___ 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] Several packages up for adoption
On 4/15/21 4:09 PM, Bojan Popovic wrote: bochs - I haven't used it in a few years. Nowadays I mostly use Qemu and Virtualbox. Hi Bojan, I'm happy to take over bochs. I find it handy for tinkering with OS devel. Kind regards, Jason ___ 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] dillo with SSL on current
pushed in my branch. Il giorno sab 17 apr 2021 alle ore 13:04 Ruben Schuller ha scritto: > > hi, > > as we are approaching 15.0 and are fixing the slackbuilds now: > i have recently fiddled with installing dillo with SSL on current. > i've had to apply a patch [1] from gentoo, run > "autoreconf -if" and compile with "-fcommon". see the attached patch > for the slackbuild. the gentoo patch is assumed to be located in > $CWD. > > cheers > ruben > > [1] > https://gitweb.gentoo.org/repo/gentoo.git/plain/www-client/dillo/files/dillo-3.0.5-openssl-1.1.patch?id=8e07d499b9d5acf45597936fef4370c0172d3247 > ___ > 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 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] SlackBuilds-users Digest, Vol 180, Issue 13
gt; To: slackbuilds-users@slackbuilds.org > Subject: Re: [Slackbuilds-users] Development Cycle Towards 15.0 > Repository SlackBuilds-users Digest, Vol 180, Issue 12 > Message-ID: > Content-Type: text/plain; charset="utf-8" > > > When submissions open again, and we will be in 15.0, which would be > > the correct time. > > > > Dave > > > >> Hi Willy, > >> When would it be possible to submit scripts for packages that only run > >> on current and that should replace outdated, no-longer maintained > >> (e.g python2-only) packages that are in the repository for 14.2 atm? > >> For example I maintain PDF-shuffler which should be dropped. This I > >> would like to replace in the 15.0 repository with PDFarranger plus Pike > >> PDF, which work fine for me on current > >> (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger > >> https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). > >> PikePDF relies on a version of qpdf not available in stock 14.2. > >> Good luck with the work ahead... > > Hi Rob > > Yes, i agree with Dave > once 15.0 repo is ready, you can submit new scripts > for now, we will focus on getting 15.0 ready first as base for future > new scripts > > > -- > Willy Sudiarto Raharjo > > -- next part -- > A non-text attachment was scrubbed... > Name: OpenPGP_signature > Type: application/pgp-signature > Size: 840 bytes > Desc: OpenPGP digital signature > URL: > <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20210417/dc7be11b/attachment-0001.asc> > > -- > > Message: 4 > Date: Fri, 16 Apr 2021 22:26:58 -0400 > From: Lenard Spencer > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] Development Cycle Towards 15.0 > Repository SlackBuilds-users Digest, Vol 180, Issue 12 > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > I have several scripts that had to be updated for 15.0. Should I just go > ahead anc zip up a tarball and send it directly to Matteo? Thanks. > > > On Fri, Apr 16, 2021, 20:34 Willy Sudiarto Raharjo > wrote: > > > > When submissions open again, and we will be in 15.0, which would be > > > the correct time. > > > > > > Dave > > > > > >> Hi Willy, > > >> When would it be possible to submit scripts for packages that only run > > >> on current and that should replace outdated, no-longer maintained > > >> (e.g python2-only) packages that are in the repository for 14.2 atm? > > >> For example I maintain PDF-shuffler which should be dropped. This I > > >> would like to replace in the 15.0 repository with PDFarranger plus Pike > > >> PDF, which work fine for me on current > > >> (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger > > >> https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). > > >> PikePDF relies on a version of qpdf not available in stock 14.2. > > >> Good luck with the work ahead... > > > > Hi Rob > > > > Yes, i agree with Dave > > once 15.0 repo is ready, you can submit new scripts > > for now, we will focus on getting 15.0 ready first as base for future > > new scripts > > > > > > -- > > Willy Sudiarto Raharjo > > > > ___ > > 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/ > > > > > -- next part ------ > An HTML attachment was scrubbed... > URL: > <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20210416/c9cf6c8b/attachment-0001.htm> > > -- > > Message: 5 > Date: Sat, 17 Apr 2021 09:28:09 +0700 > From: Willy Sudiarto Raharjo > To: slackbuilds-users@slackbuilds.org > Subject: Re: [Slackbuilds-users] Development Cycle Towards 15.0 > Repository SlackBuilds-users Digest, Vol 180, Issue 12 > Message-ID: <61e3dbb1-373f-96ef-27ed-4b016c4dd...@slackbuilds.org> > Content-Type: text/plain; charset="utf-8" > > > I have several scripts that had to be updated for 15.0. Should I just go > > ahead anc zip up a tarball and send it directly to Matteo? Thanks. > > Please wait until i pushed public update this weekend
Re: [Slackbuilds-users] Development Cycle Towards 15.0 Repository
pushed in my branch. Il giorno sab 17 apr 2021 alle ore 14:02 Alexander Verbovetsky ha scritto: > > Hello, > > I'd like to ask to remove r2e. > > We have rss2email, which is the modern version of this program. ___ 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] Regarding Fixes and Patches for 15.0
Hello all, May I request that people hold on to their 15.0 patches and fixes for now, rather than posting them to the list? They really need to go through the usual submission system once we reopen it, so that they get added to the database properly, or via git if you use that method. Thanks! -- Dave ___ 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] Development Cycle Towards 15.0 Repository
Hello, I'd like to ask to remove r2e. We have rss2email, which is the modern version of this program. Best regards, Alexander ___ 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] dillo with SSL on current
hi,
as we are approaching 15.0 and are fixing the slackbuilds now:
i have recently fiddled with installing dillo with SSL on current.
i've had to apply a patch [1] from gentoo, run
"autoreconf -if" and compile with "-fcommon". see the attached patch
for the slackbuild. the gentoo patch is assumed to be located in
$CWD.
cheers
ruben
[1]
https://gitweb.gentoo.org/repo/gentoo.git/plain/www-client/dillo/files/dillo-3.0.5-openssl-1.1.patch?id=8e07d499b9d5acf45597936fef4370c0172d3247
--- dillo.SlackBuild 2021-04-17 12:54:37.268747016 +0200
+++ dillo.SlackBuild.new 2021-04-17 13:03:05.481754016 +0200
@@ -71,11 +71,15 @@
\( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
-o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
+patch -p1 < $CWD/dillo-3.0.5-openssl-1.1.patch
+
+autoreconf -if
+
#https and ssl are in the alpha stage, but if you don't want to try and use it
#just delete or comment out --enable-ssl
-CFLAGS="$SLKCFLAGS" \
-CXXFLAGS="$SLKCFLAGS" \
+CFLAGS="$SLKCFLAGS -fcommon" \
+CXXFLAGS="$SLKCFLAGS -fcommon" \
./configure \
--enable-ssl \
--prefix=/usr \
___
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] My -current scripts
Il giorno sab 17 apr 2021 alle ore 08:18 Eugen Wissner ha scritto: > > Hi, > > I would like to ask to remove the following SlackBuilds: > > - gcc-d: Part of Slackware current > - gkrellm-volume: The home page and download link are dead, I'm not sure > if this software still exists > - oniguruma: In Slackware current > - opendbx: It builds on current, but opendbx doesn't seem to be active, > the last release was in 2012 and nothing depends on it. > - tanya: It is my own development; I wasn't working on it a lot in the > last time and I'm not sure I will. Anyway it is not the best way to > build D dependencies. I've pushed these in my branch. Matteo ___ 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/
