From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 5/5] perl-File-Tail: Update to 1.3
Date: Mon, 22 Mar 2021 08:25:29 +0100 [thread overview]
Message-ID: <20210322072529.1229-1-adolf.belka@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2571 bytes --]
- Update from 0.99.3 to 1.3
- No update required to rootfile
- perl-File-Tail is a dependency of the swatch addon
- Changelog
1.0 Actually just two minor bug fixes (one of them in a test), but I no
longer see a point in not having a 1.0 version.
1.1 Lee Duncan drew my attention to Stephan Muller's fixes for Windows compatibility
Changed the use of the system's mv command to using File::Copy in the
tests. (Steffen Mueller)
Added machine-readable license statement to Makefile.PL and thus
META.yml (Steffen Mueller)
The sixth test in 10/open.t is skipped on win32 because you can't just
move files around that are opened. (Steffen Mueller)
Due to using sysread and friends, there were newline problems on win32.
That should be fixed now. (Steffen Mueller)
1.2 Break the infinite loop that can result when the average length of lines
causes the attempt to fill the tail buffer to fill with the exact same
or even smaller number of lines.
1.3 Fix for a stupid bug in 1.2 (GFILATOV, Slaven_Rezic)
Added a warning for use of debug in a non-debug version of File::Tail
Shows a warning when maxbuf is set to a too-small value
Invoking name_changes callback changes the value of input attribute (sottile(a)ix.netcom.com)
When deciding to reopen the file, check if the inode matches (that would mean it has not
been ranamed)
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
lfs/perl-File-Tail | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lfs/perl-File-Tail b/lfs/perl-File-Tail
index c9b4cbde4..fb82d4e78 100644
--- a/lfs/perl-File-Tail
+++ b/lfs/perl-File-Tail
@@ -24,7 +24,7 @@
###############################################################################
include Config
-VER = 0.99.3
+VER = 1.3
THISAPP = File-Tail-$(VER)
DL_FILE = ${THISAPP}.tar.gz
@@ -33,7 +33,7 @@ DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = perl-File-Tail
DEPS =
-PAK_VER = 4
+PAK_VER = 5
###############################################################################
# Top-level Rules
@@ -43,7 +43,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = ef0fb7bcb4181ba593f4a09940f61d1c
+$(DL_FILE)_MD5 = 252635f89ec18cb871c0b45ed64b3f63
install : $(TARGET)
--
2.31.0
reply other threads:[~2021-03-22 7:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210322072529.1229-1-adolf.belka@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