Eric Sunshine <sunshine@xxxxxxxxxxxxxx> writes: > On Wed, Sep 5, 2018 at 4:29 AM Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> wrote: >> I recently gained access to a Solaris 10 SPARC (5.10) box and discovered >> that the chainlint.sed implementation in 2.19.0 has more sed portability >> issues. >> >> First, whoever implemented the /bin/sed on Solaris apparently read the >> POSIX requirements for a max length label of 8 to mean that 8 characters >> should include the colon, so a bunch of things fail because of that, but >> are fixed with a shorter 7 character label. > > I'm pretty sure that Solaris 'sed' predates POSIX by a good bit, but > that's neither here nor there. I thought that we long time ago declared that it is a lost cause to use Solaris with only tools in /bin and /usr/bin and instead depend on /usr/xpg[46]/bin; did something happen recently to make us reconsider the position? If not, let's not waste time worrying about /bin/sed over there.
