Date: Tue, 27 Jan 2015 17:35:36 -0800
From: Isaac Dunham <ibid.ag@gmail.com>
To: Natanael Copa <ncopa@alpinelinux.org>
Cc: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] considering packaging another mailx
Message-ID: <20150128013455.GB1798@newbook>
References: <20140913203317.GA5578@newbook>
 <20140915104643.25dea7f5@ncopa-desktop.alpinelinux.org>
 <20140915143728.GA514@muslin>
 <20150127161535.698aa7dd@ncopa-desktop.alpinelinux.org>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150127161535.698aa7dd@ncopa-desktop.alpinelinux.org>
User-Agent: Mutt/1.5.23 (2014-03-12)

On Tue, Jan 27, 2015 at 04:15:35PM +0100, Natanael Copa wrote:
> I'm bringing up this old issue because there are a couple of CVE issues:
> http://seclists.org/oss-sec/2014/q4/1066
> 
> Do you think it would be possible to completely replace main/mailx with
> heirloom-mailx without breaking too much? More specifically, does
> heirloom/mailx' mail implementation support all the args in current
> mail/mailx?
> 
> -nc

Yes.
heirloom-mailx does not mention -v in its help, but seems to accept it.
Other options/arguments seem to be compatible.

> 
> > Now, a note: If heirloom-mailx gets renamed to mailx, it will need one
> > alteration:
> > I'm using the package name to rename mailx.1 so it doesn't conflict with
> > man-pages.
> > In my experiene, the magic that the fts APKBUILD uses to try to avoid
> > installing fts-doc along with man-pages doesn't work, so I'd rather not
> > duplicate it.

Thanks,
Isaac Dunham


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---