From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 3/3] perl-Net-SMTP-SSL: Update to 1.04
Date: Mon, 22 Mar 2021 08:44:24 +0100 [thread overview]
Message-ID: <9ad0a1f3-2b2d-8fcd-7141-8b22f2f7d710@ipfire.org> (raw)
In-Reply-To: <20210322073324.1943-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2107 bytes --]
Hi All,
When updating this dependency of git I saw that it was now deprecated. I
had a look at the replacement library and while I could create it as a
new addon, it was not clear to me if just defining it as a dependency of
git would make git correctly use it.
I am also not sure why anyone would want to run git on a firewall. This
addon is not listed in the wiki.
I am therefore not sure if this patch set should be merged or if it
should be updated with the new library (and how) or if git should still
be left in IPFire as an addon and hence this library.
I am open to whatever decision you think is appropriate for this patch set.
Regards,
Adolf.
On 22/03/2021 08:33, Adolf Belka wrote:
> - Update from 1.02 to 1.04
> - Update of rootfile not required
> - This is a dependency of git addon package
> - Changelog
> 1.04 2016-10-09
> - mark this library deprecated, suggest newer Net::SMTP instead
> 1.03 2015-06-20
> - $net_smtp_ssl->isa('Net::SMTP') is now true
>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> lfs/perl-Net-SMTP-SSL | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/lfs/perl-Net-SMTP-SSL b/lfs/perl-Net-SMTP-SSL
> index 90e8a2260..2bb00a808 100644
> --- a/lfs/perl-Net-SMTP-SSL
> +++ b/lfs/perl-Net-SMTP-SSL
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 1.02
> +VER = 1.04
>
> THISAPP = Net-SMTP-SSL-$(VER)
> DL_FILE = ${THISAPP}.tar.gz
> @@ -33,7 +33,7 @@ DIR_APP = $(DIR_SRC)/$(THISAPP)
> TARGET = $(DIR_INFO)/$(THISAPP)
> PROG = perl-Net-SMTP-SSL
> DEPS =
> -PAK_VER = 2
> +PAK_VER = 3
>
> ###############################################################################
> # Top-level Rules
> @@ -43,7 +43,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = e67b4d842a51b9a453aeeaeed45fb8e1
> +$(DL_FILE)_MD5 = 62b49c961043898b43b041dafbc1b389
>
> install : $(TARGET)
>
>
--
Sent from my laptop
next prev parent reply other threads:[~2021-03-22 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 7:33 Adolf Belka
2021-03-22 7:44 ` Adolf Belka [this message]
2021-03-22 11:19 ` Michael Tremer
2021-03-22 11:52 ` Adolf Belka
2021-03-22 13:45 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9ad0a1f3-2b2d-8fcd-7141-8b22f2f7d710@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox