summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS33
1 files changed, 17 insertions, 16 deletions
diff --git a/NEWS b/NEWS
index bbb6b5888..803d89c69 100644
--- a/NEWS
+++ b/NEWS
@@ -1,19 +1,20 @@
-Known issue not fixed in 1.8.3c:
-
- Historically Automake has always generated V7 format tarballs during
- `make dist'. This format is quite antiquated, but is portable. It
- supports filenames with up to 99 characters. When given longer
- filenames some tar implementations will diagnose the problem while
- other will generate broken or non-V7 tarballs. For instance GNU tar
- 1.13.25 will produce an archive with GNU extensions, while the
- latest GNU tar beta (1.13.93) will truncate filenames.
-
- We are working an a new scheme for Automake 1.9 that will allow
- newer tar formats to be used. In the meantime, for people who
- cannot avoid long filenames in their packages we recommand sticking
- to GNU tar 1.13.25 and not installing newer versions.
-
-Bugs fixed in 1.8.3c:
+Known issue not fixed in 1.8.4:
+
+ Historically Automake has always tried to generate V7 format
+ tarballs during `make dist'. This format is quite antiquated, but
+ is portable. It supports filenames with up to 99 characters. When
+ given longer filenames some tar implementations will diagnose the
+ problem while other will generate broken or non-V7 tarballs. For
+ instance GNU tar 1.13.25 will produce an archive with GNU
+ extensions, while the latest GNU tar beta (1.13.93) will silently
+ truncate filenames.
+
+ Automake 1.9 will have options to select newer tar formats, and
+ diagnose long filenames. In the meantime we recommand that people
+ who cannot avoid long filenames in their packages stick to GNU tar
+ 1.13.25.
+
+Bugs fixed in 1.8.4:
* Long standing bugs: