A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1827 
====================================================================== 
Reported By:                nrk
Assigned To:                
====================================================================== 
Project:                    Issue 8 drafts
Issue ID:                   1827
Category:                   Shell and Utilities
Type:                       Enhancement Request
Severity:                   Objection
Priority:                   normal
Status:                     New
Name:                       NRK 
Organization:                
User Reference:              
Section:                    compress(1) utility 
Page Number:                n/a 
Line Number:                n/a 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2024-04-15 03:23 UTC
Last Modified:              2024-04-17 11:03 UTC
====================================================================== 
Summary:                    Standardize gzip(1) cli interface instead of adding
it to compress(1)
====================================================================== 

---------------------------------------------------------------------- 
 (0006762) oguzismailuysal (reporter) - 2024-04-17 11:03
 https://austingroupbugs.net/view.php?id=1827#c6762 
---------------------------------------------------------------------- 
Re: https://austingroupbugs.net/view.php?id=1827#c6761

<blockquote>Both the gzip file-format and the underlying algorithm
(DEFLATE) are *entirely different* to LZW.</blockquote>
<blockquote>Most other compression algorithms (bzip2, zstandard etc) in use
are in similar boat where they are all vastly different to one
another.</blockquote>
Doesn't matter as long as they can be used for compressing arbitrary data.
They all take a parameter specifying the compression level which can be
relayed through the option <b>-b</b> if <b>compress</b> were to be
implemented as a wrapper for standalone utilities. POSIX defines the
interface, how it is implemented is outside the standard's scope.

<blockquote>So in cases where an implementation wants to support both
algorithms, the current state of compress(1) is not "less demanding" and
saves them no work.</blockquote>
It does, though. The interface is already there, implementing only the
algorithm is less work than implementing both the algorithm and a separate
interface. Documenting a single option argument is also less work than
documenting a whole new utility.

<blockquote>Not to mention, any implementation that wants to be useful in
practice will need to ship gzip(1) anyways.</blockquote>
That's an opinion.

<blockquote>Currently if I want to provide a posix-compliant compress(1)
tool, I only need to worry about LZW. Or if gzip(1) was standardized, and I
wanted to provide posix-compliant gzip(1) I'd only need to worry about
DEFLATE. But in the current draft, implementating a posix-compliant
compress(1) requires me to both implement LZW and DEFLATE.</blockquote>
I don't see a problem here. You can choose to comply with an older version
of POSIX or not comply with POSIX at all. 

You keep mentioning "distros", I assume you mean Linux distributions. No
Linux distribution is certified to be POSIX-conformant and I doubt any of
them try to be so. So, what "distros" do is irrelevant here. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2024-04-15 03:23 nrk            New Issue                                    
2024-04-15 03:23 nrk            Name                      => NRK             
2024-04-15 03:23 nrk            Section                   => compress(1) utility
2024-04-15 03:23 nrk            Page Number               => n/a             
2024-04-15 03:23 nrk            Line Number               => n/a             
2024-04-15 03:24 nrk            Issue Monitored: nrk                         
2024-04-16 05:57 dannyniu       Note Added: 0006752                          
2024-04-16 05:58 dannyniu       Note Edited: 0006752                         
2024-04-16 18:39 steffen        Note Added: 0006753                          
2024-04-16 22:51 nrk            Note Added: 0006754                          
2024-04-16 23:03 nrk            Note Added: 0006755                          
2024-04-16 23:32 oguzismailuysalNote Added: 0006756                          
2024-04-17 00:10 steffen        Note Added: 0006757                          
2024-04-17 00:32 nrk            Note Added: 0006758                          
2024-04-17 01:36 larryv         Note Added: 0006759                          
2024-04-17 06:16 oguzismailuysalNote Added: 0006760                          
2024-04-17 06:18 oguzismailuysalNote Edited: 0006760                         
2024-04-17 06:19 oguzismailuysalNote Edited: 0006760                         
2024-04-17 07:47 nrk            Note Added: 0006761                          
2024-04-17 11:03 oguzismailuysalNote Added: 0006762                          
======================================================================


  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to